Digital video recording/playback system with entry point processing function

ABSTRACT

This invention allows the user to insert an entry point (bookmark) at an arbitrary recording position of video data, audio data, and the like as if he or she placed a bookmark between pages of a book. Information RTR_VMG that manages recorded objects includes movie cell entry point information M_C_EPI. M_C_EPI includes entry point playback time information EP_PTM and text information PRM_TXTI that pertains to an entry point. PRM_TXTI can store text information that pertains to its contents together with type information and date information of an entry point.

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application is based upon and claims the benefit of priorityfrom the prior Japanese Patent Application No. 11-131475, filed May 12,1999, the entire contents of which are incorporated herein by reference.

BACKGROUND OF THE INVENTION

[0002] The present invention relates to an apparatus/method capable ofreal-time digital recording of a video picture and the like, and adigital information medium (real-time digital video recording/playbacksystem) used in the apparatus/method.

[0003] More particularly, the present invention relates to anapparatus/method which assures a special information storage area on arecordable/reproducible DVD disc (DVD-RAM disc or the like), and usesinformation stored in that area as needed upon playback, erasure, or thelike of a recorded video program.

[0004] Nowadays, DVD video specification that uses MPEG2 (Moving PictureExpert Group 2) in video (moving picture) digital recording/playback,and AC-3 (Digital Audio Compression or Audio Coding 3) in audio digitalrecording/playback has been settled, and various playback apparatuses(DVD video players) which use that specification are commerciallyavailable.

[0005] The DVD video specification supports MPEG2 as a moving picturecompression scheme, and AC-3 audio and MPEG audio in addition to linearPCM as an audio recording scheme. Also, the DVD video specificationsupports sub-picture data for superimposed dialogs, navigation data forplayback control such as fastforwarding, rewinding, data search, and thelike, and ISO9660 and UDF bridge format for computers.

[0006] Furthermore, recordable DVD discs (recordable/reproducibleDVD-RAM/DVD-RW or write-once DVD-R) have been developed, and anenvironment that allows the development of digital video informationrecording/playback apparatuses (alternatives to a conventional videocassette tape recorder) using recordable DVD discs is in order.

[0007] Under such circumstances, the DVD-RTR (DVD real-time recording)specification for digitally recording a video picture or the like inreal time and playing it back has been proposed, and is settled as astandard.

[0008] However, the number and kinds of program contents recorded tendsto increase wish increasing recording size of a disc, and it becomesharder for the user to grasp the recorded contents. For this reason, aproblem is posed in terms of management of recorded discs.

BRIEF SUMMARY OF THE INVENTION

[0009] It is an object of the present invention to provide anapparatus/method and medium, which allow the user to write or erase amark (entry point) at an arbitrary recording position of video data,audio data, and the like as if he or she placed a bookmark between pagesor at an important position while reading a book.

[0010] In order to achieve the above object, a digital video informationmedium according to the present invention has a volume space including amanagement area and data area.

[0011] The data area stores data segmented into one or more objects(RTR_MOV.VRO/VR_MOVIE.VRO, RTR_STO.VRO/VR_STILL.VRO,RTR_STA.VRO/VR_AUDIO.VRO). Each object is comprised of one or more dataunits (one or more VOBUs form a cell, and one or more cells form videoobject). Each data unit (VOBU) stores one or more packs (video or audiopacks) of video or audio data to be played back within a predeterminedtime (0.4 to 1.2 sec).

[0012] The management area stores management information (RTR_VMG) usedto manage the objects. The management information (RTR_VMG) has programchain information (ORG_PGCI or UD_PGCIT) for designating the playbackorder of objects. The program chain information (PGCI) includes one ormore pieces of program information (PGI) and one or more pieces of cellinformation (CI). The cell information (CI) contains designationinformation (M_CI) for designating an object to be played back.

[0013] The designation information (M_CI) records entry pointinformation (M_C_EPI) for designating the playback position in anobject.

[0014] The entry point information (M_C_EPI) includes information(PRM_TXTI) that pertains to an entry point.

[0015] In order to achieve the above object, a digital video informationrecording/playback apparatus according to the present invention recordsor plays back the contents of the objects (RTR_MOV.VRO/VR_MOVIE.VRO)using a recordable/reproducible medium which has movie cell information(M_CI) in management information (RTR_VMG) for managing objects(RTR_MOV.VRO/VR_MOVIE.VRO) as recorded information.

[0016] The digital video information recording/playback apparatuscomprises an entry point setting unit (MPU) for setting a required entrypoint (M_C_EPI#1 to M_C_EPI#n) in the movie cell information (M_CI); anadditional information input unit (MPU) for inputting additionalinformation (information type, information date, text information, andthe like in PRM_TXTI) with respect to the entry point (M_C_EPI); and anadditional information setting unit (MPU) for setting the additionalinformation in the entry point (M_C_EPI).

[0017] In order to achieve the above object, a digital video informationprocessing method according to the present invention records or playsback the contents of the objects (RTR_MOV.VRO/VR_MOVIE.VRO) using arecordable/reproducible medium which has movie cell information (M_CI)in management information (RTR₁₃ VMG) for managing objects(RTR_MOV.VRO/VR_MOVIE.VRO) as recorded information.

[0018] In this digital video information processing method, a requiredentry point (M_C_EPI#1 to M_C_EPI#n) is set in the movie cellinformation (M_CI); additional information (information type,information date, text information, and the like in PRM_TXTI) is inputwith respect to the entry point (M_C_EPI); and the additionalinformation is set in the entry point (M_C_EPI).

[0019] Using the entry point as needed, the user can easily recognizethe recorded contents of a disc. Also, using the entry pointinformation, the user can record/play back from a desired position.

[0020] Additional objects and advantages of the invention will be setforth in the description which follows, and in part will be obvious fromthe description, or may be learned by practice of the invention. Theobjects and advantages of the invention may be realized and obtained bymeans of the instrumentalities and combinations particularly pointed outhereinafter.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING

[0021] The accompanying drawings, which are incorporated in andconstitute a part of the specification, illustrate presently preferredembodiments of the invention, and together with the general descriptiongiven above and the detailed description of the preferred embodimentsgiven below, serve to explain the principles of the invention.

[0022]FIG. 1 is a view for explaining the structure of arecordable/reproducible optical disc according to an embodiment of thepresent invention;

[0023]FIG. 2 is a view for explaining the format of digital informationrecorded on the optical disc shown in FIG. 1;

[0024]FIG. 3 is a view for explaining the data structure of a videoobject shown in FIG. 2;

[0025]FIG. 4 is a view for explaining the data structure of a dummy packshown in FIG. 3;

[0026]FIG. 5 is a view for explaining the file structure of digitalinformation recorded on the optical disc shown in FIG. 1;

[0027]FIG. 6 is a view for explaining the data structure of a navigationdata file (RTR_VMG) shown in FIG. 5;

[0028]FIG. 7 is a view for explaining the contents of a video managerinformation table (VMGI_MAT) shown in FIG. 6;

[0029]FIG. 8 is a view for explaining the data structure of a play listsearch pointer table (PL_SRPT) shown in FIG. 6;

[0030]FIG. 9 is a view for explaining the contents of play list searchpointer table information (PL_SRPTI) shown in FIG. 8;

[0031]FIG. 10 is a view for explaining the contents of a play listsearch pointer (PL_SRP) shown in FIG. 8;

[0032]FIG. 11 is a view for explaining the contents of thumbnail pointerinformation (THM_PTRI) shown in FIG. 10;

[0033]FIG. 12 is a view for explaining the data structure of a movie AVfile information table (M_AVFIT) shown in FIG. 6;

[0034]FIG. 13 is a view for explaining the data structure of movie VOBinformation (M_VOBI) shown in FIG. 12;

[0035]FIG. 14 is a view for explaining the data structure of time mapinformation (TMAPI) shown in FIG. 13;

[0036]FIG. 15 is a view for explaining the contents of time map generalinformation (TMAP_GI) shown in FIG. 14;

[0037]FIG. 16 is a view for explaining the contents of a time entry(TM_ENT) shown in FIG. 14;

[0038]FIG. 17 is a view for explaining the data structure of a userdefined PGC information table (UD_PGCIT) shown in FIG. 6;

[0039]FIG. 18 is a view for explaining the data structure of a text datamanager (TXTDT_MG) shown in FIG. 6;

[0040]FIG. 19 is a view for explaining the data structure of PGCinformation (PGCI; original PGC or user defined PGC information);

[0041]FIG. 20 is a view for explaining the contents of PGC generalinformation (PGC_GI) shown in FIG. 19;

[0042]FIG. 21 is a view for explaining the contents of programinformation (PGI) shown in FIG. 19;

[0043]FIG. 22 is a view for explaining the data structure of cellinformation (CI) shown in FIG. 19;

[0044]FIG. 23 is a view for explaining the data structure of movie cellinformation (M_CI) shown in FIG. 22;

[0045]FIG. 24 is a view for explaining the contents of movie cellgeneral information (M_C_GI) shown in FIG. 23;

[0046]FIG. 25 is a view for explaining the contents of movie cell entrypoint information (M_C_EPI) shown in FIG. 23;

[0047]FIG. 26 is a view for explaining a use example of primary textinformation (PRM_TXTI);

[0048]FIG. 27 is a view for explaining a correspondence among programsthat form a program set, and program parts that form a play list;

[0049]FIG. 28 is a view for explaining a correspondence between thepresentation start times/presentation end times of cells that form auser defined PGC (or original PGC), and the offset addresses for VOBUsof VOBs that form a movie video object (RTR_MOV.VRO/VR_MOVIE.VRO) shownin FIG. 5;

[0050]FIG. 29 is a block diagram for explaining an example of thearrangement of an apparatus (RTR video recorder) for recording a videoprogram or the like in real time and playing it back using therecordable/reproducible optical disc shown in FIG. 1;

[0051]FIG. 30 is a flow chart for explaining an example of recording inthe apparatus shown in FIG. 29;

[0052]FIG. 31 is a flow chart for explaining an example of playback inthe apparatus shown in FIG. 29;

[0053]FIG. 32 is a flow chart for explaining an example of an entrypoint enter process in the apparatus shown in FIG. 29;

[0054]FIG. 33 is a flow chart for explaining an example of an automaticentry point enter process (for entering entry points at given timeintervals) in the apparatus shown in FIG. 29;

[0055]FIG. 34 is a flow chart for explaining an example of a textinformation input process in the apparatus shown in FIG. 29;

[0056]FIG. 35 shows an example of a text information input window in thetext information input process shown in FIG. 34;

[0057]FIG. 36 is a view for explaining an example of the relationshipamong recorded video data, entry points, and information (attribute,recording date, and the like) of the recorded video data in an opticaldisc recorded by the apparatus shown in FIG. 29;

[0058]FIG. 37 is a view for explaining another example of therelationship among recorded video data, entry points, and information(attribute, recording date, and the like) of the recorded video data inan optical disc recorded by the apparatus shown in FIG. 29;

[0059]FIG. 38 is a flow chart showing an example of a playback menudisplay process in the apparatus shown in FIG. 29;

[0060]FIG. 39 shows an example of a playback menu display window in theplayback menu display process shown in FIG. 38;

[0061]FIG. 40 is a flow chart for explaining an example of a textinformation search process in the apparatus shown in FIG. 29;

[0062]FIG. 41 shows an example of a search keyword input window in thetext information search process shown in FIG. 40;

[0063]FIG. 42 shows an example of a search result display window in thetext information search process shown in FIG. 40;

[0064]FIG. 43 is a flow chart for explaining an example of a defectenter process in the apparatus shown in FIG. 29;

[0065]FIG. 44 is a view for explaining an example of the relationshipbetween defective portions of recorded video data detected by theprocess shown in FIG. 43, and entry points;

[0066]FIG. 45 shows a display example of defective portions of recordedvideo data detected by the process shown in FIG. 43, and theirreproduction manners;

[0067]FIG. 46 is a flow chart for explaining an example of a process forentering the priority order of erasure in the apparatus shown in FIG.29;

[0068]FIG. 47 is a view for explaining an example of the relationshipamong recorded video data, entry points, and information (attribute,recording date, and the like) of the recorded video data detected by theprocess shown in FIG. 46;

[0069]FIG. 48 shows a display example of information (recording time,title, thumbnail, last playback date, and the like) of recorded videodata detected by the process shown in FIG. 46, and its order of erasure;

[0070]FIG. 49 explains a structure of one stream pack used when astreamer is used for a DVD-RTR recorder;

[0071]FIG. 50 shows details of the inner structure of the stream packshown in FIG. 49;

[0072]FIG. 51 briefly illustrates entry point relating information withrespect to movie cell information (M_CI) used for an RTR recorder;

[0073]FIG. 52 briefly illustrates entry point relating information withrespect to still picture cell information (S_CI) used for an RTRrecorder; and

[0074]FIG. 53 briefly illustrates entry point relating information withrespect to stream cell information (SCI) used for a streamer.

DETAILED DESCRIPTION OF THE INVENTION

[0075] The arrangement of a medium (DVD recordable/reproducible disc)according to an embodiment of the present invention, the arrangement ofa DVD-RTR (DVD real-time recording) recording/playback apparatus (RTRvideo recorder), and various operations of this apparatus will beexplained below with reference to the accompanying drawings.

[0076]FIG. 1 is a view for explaining the structure of optical disc 10used in the DVD-RTR recording/playback apparatus. As shown in FIG. 1,optical disc 10 has a structure obtained by adhering a pair oftransparent substrates 14 respectively having layers 17A and 17B usingadhesive layer 20.

[0077] If this disc 10 is a single layered DVD-RAM (or DVD-RW) disc,first information recording layer 17A is formed of a phase changerecording layer, and second information recording layer 17B is formed ofa dummy layer (which may also serve as a label of that disc).

[0078] If this disc 10 is a single-sided, two-layered DVD-ROM/RAM disc,first information recording layer 17A is formed of a semi-transparentfilm (thin metal film or the like) formed with pits, and secondinformation recording layer 17B is formed of a phase change recordinglayer.

[0079] If this disc 10 is a double-sided, two-layered DVD-RAM (orDVD-RW) disc, both first and second information recording layers 17A and17B are formed of phase change recording layers.

[0080] Each substrate 14 can be formed of a 0.6-mm thick polycarbonatefilm, and adhesive layer 20 can consist of a very thin ultravioletsetting resin (around 40 m to 70 m thick). When this pair of 0.6-mmthick substrates 14 are adhered so that layers 17A and 17B contact eachother on the surfaces of adhesive layer 20, 1.2-mm thick large-capacityoptical disc 10 is obtained.

[0081] Optical disc 10 has center hole 22, and clamp areas 24 used forclamping optical disc 10 upon its rotation are formed around center hole22 on the two surfaces of the disc. Center hole 22 receives the spindleof a disc motor when disc 10 is loaded into a disc drive (not shown).Optical disc 10 is clamped at its clamp areas 24 by a disc clamper (notshown).

[0082] Optical disc 10 has information areas 25 that can recordinformation such as video data, audio data, and the like around clampareas 24.

[0083] Each information area 25 has lead-out area 26 on its outerperiphery side, and lead-in area 27 on its inner periphery side thatcontacts clamp area 24. The area between lead-out and lead-in areas 26and 27 is defined as data recording area 28.

[0084]FIG. 1 also exemplifies the correspondence between each datarecording area 28 of optical disc 10 and a data recording track recordedthere.

[0085] On each of recording layers 17A and 17B of information areas 25,a recording track is continuously formed in, e.g., a spiral pattern. Thecontinuous track is segmented into a plurality of sectors, which haveserial numbers. various data are recorded on optical disc 10 using thesesectors as recording units.

[0086] Data recording area 28 serves as an actual data recording area,and records video data (main picture data) such as a movie or the like,sub-picture data such as superimposed dialogs, menus, and the like, andaudio data such as words, effect sounds, and the like asrecording/playback information in the form of similar pit trains(physical shapes or phase states that bring about change in opticalconditions).

[0087] When optical disc 10 is a double-sided recording RAM disc inwhich each surface has one recording layer, each of recording layers 17Aand 17B can be formed by three layers, i.e., by sandwiching aphase-change recording material layer (e.g., Ge2Sb2Te5) between two zincsulfide.silicon oxide (ZnS.SiO2) mixture layers.

[0088] When optical disc 10 is a single-sided recording RAM disc inwhich each surface has one recording layer, recording layer 17A on theside of read-out face 19 can be formed by three layers including theaforementioned phase-change recording material layer. In this case,layer 17B on the side opposite to read-out face 19 need not be aninformation recording layer but may merely be a dummy layer.

[0089] When optical disc 10 is a one-side read type two-layered RAM/ROMdisc, two recording layers 17A and 17B can comprise single phase-changerecording layer 17B (on the side farther from read-out face 19;read/write), and single semi-transparent metal reflection layer 17A (onthe side closer to read-out face 19; read-only).

[0090] When optical disc 10 is a write-once DVD-R, a polycarbonatesubstrate is used, gold can be used as a reflection layer (not shown),and an ultraviolet setting resin can be used as a protection layer (notshown). In this case, an organic dye is used in recording layer 17A or17B. As the organic dyes, cyanine, squarilium, chroconic, andtriphenylmenthane dyes, xanthene and quinone dyes (naphthoquinone,anthraquinone, and the like), metal complex dyes (phthalocyanine,porphyrin, dithiol complex, and the like), and so forth can be used.

[0091] Data can be written on such DVD-R disc using a semiconductorlaser having a wavelength of 650 nm and an output of around 6 to 12 mW.

[0092] In various types of optical discs 10 described above, read-onlyROM information is recorded on the recording layer as an embossedpattern signal. By contrast, no such embossed pattern signal is formedon substrate 14 having a read/write (or write-once) recording layer, anda continuous groove is formed instead. A phase-change recording layer isformed on such groove. In case of a read/write DVD-RAM disc, thephase-change recording layer in land portions is also used forinformation recording in addition to the groove.

[0093] When optical disc 10 is of one-side read type (independently ofone or two recording layers), substrate 14 on the rear side viewed fromread-out face 19 need not always be transparent to the read/write laserbeam used. In this case, a label may be printed on the entire surface ofsubstrate 14 on the rear side.

[0094] A DVD-RTR recorder/player (to be described later) can be designedto attain repetitive recording/repetitive playback (read/write) for aDVD-RAM disc (or DVD-RW disc), single recording/repetitive playback fora DVD-R disc, and repetitive playback for a DVD-ROM disc.

[0095] When disc 10 is a DVD-RAM (or DVD-RW), disc 10 itself is storedin cartridge 11 to protect its delicate disc surface.

[0096] When DVD-RAM disc 10 in cartridge 11 is inserted into the discdrive of a DVD-RTR recorder/player (to be described later), disc 10 ispulled out from cartridge 11, is clamped by the turntable of a spindlemotor (not shown), and is rotated to face an optical head (not shown).

[0097] On the other hand, when disc 10 is a DVD-R or DVD-ROM, disc 10itself is not stored in cartridge 11, and bare disc 10 is directly seton the disc tray of a disc drive.

[0098] Recording layer 17 of information area 25 shown in FIG. 1 isformed with a continuous data recording track in a spiral pattern. Thecontinuous track is segmented into a plurality of logical sectors(minimum recording units) each having a given storage size, as shown inFIG. 1, and data are recorded with reference to these logical sectors.The recording size per logical sector is determined to be 2,048 bytes(or 2 kbytes) which are equal to one pack data length (to be describedlater).

[0099] Data recording area 28 is an actual data recording area, whichsimilarly records management data, main picture (video) data,sub-picture data, and audio data.

[0100] Note that data recording area 28 of disc 10 can be segmented intoa plurality of ring-shaped (annular) recording areas (a plurality ofrecording zones), although not shown. The disc rotational velocityvaries in units of recording zones. However, within each zone, aconstant linear or angular velocity can be set. In this case, anauxiliary recording area (free space) can be provided for each zone.These free spaces in units of zones may collectively form a reserve areafor that disc 10.

[0101]FIG. 2 is a view for explaining the hierarchical structure ofinformation recorded on optical disc 10 shown in FIG. 1.

[0102] In this structure, lead-in area 27 includes an embossed data zonewhose light reflection surface has an embossed pattern, a mirror zonewhose surface is flat (mirror surface), and a rewritable data zonecapable of information rewrites. Lead-out area 26 is also made up of arewritable data zone capable of information rewrites.

[0103] Data recording area (volume space) 28 is comprised of volume/filemanagement information 70 and data area DA, which can be rewritten bythe user.

[0104] Volume/file management information 70 records file information ofaudio/video data recorded on data area DA, and information that pertainsto the entire volume.

[0105] Data area DA can have both areas DA1 and DA3 that record computerdata, and audio/video data area DA2 that records video data/audio dataand the like. Note that the recording order, recording information size,and the like of computer data and audio/video data are arbitrary. Dataarea DA can record computer data or audio/video data alone.

[0106] Audio/video data area DA2 includes control information DA21,video object DA22, picture object DA23, and audio object DA24.

[0107] Control information DA21 can include control information requiredupon executing various processes such as recording (image recordingand/or audio recording), playback, edit, search, and the like.

[0108] Video object DA22 can include information of the contents ofrecorded video data.

[0109] Picture object DA23 can include still image information such asstill images, slide images, and the like.

[0110] Audio object DA24 can include information of the contents ofrecorded audio data.

[0111] Note that video object DA22 is formed by video object set VOBS.This VOBS has contents corresponding to one or more program chains PGC#lto PGC#k which respectively designate cell playback orders by differentmethods.

[0112] The embossed data zone of lead-in area 27 records in advance:

[0113] (1) information which pertains to the entire information storagemedium: the disc type (a DVD-ROM, DVD-RAM (or DVD-RW), DVD-R, or thelike); disc size (12 cm, 8 cm, or the like); recording density; physicalsector numbers indicating the recording start/end positions, and thelike;

[0114] (2) information which pertains to the recording/playback/erasurecharacteristics: the recording power and recording pulse width; erasepower; playback power; linear velocity upon recording and erasure, andthe like; and

[0115] (3) information which pertains to the manufacture of eachinformation storage medium: the manufacturing number and the like.

[0116] The rewritable zone of each of lead-in area 27 and lead-out area26 includes:

[0117] (4) a field for recording a unique disc name of each informationrecording medium;

[0118] (5) a test recording field (for confirming recording/erasureconditions); and

[0119] (6) a field for recording management information that pertains todefective fields in data area DA.

[0120] On fields (4) to (6), a DVD-RTR recorder/player (a RTR videorecorder or a personal computer with a DVD-RAM drive) can recordinformation.

[0121] When disc 10 is set in the DVD-RTR recorder/player (RTR videorecorder), information on lead-in area 27 is read first. Lead-in area 27records a predetermined reference code and control data in ascendingorder of sector numbers.

[0122] The reference code in lead-in area 27 is made up of two errorcorrection code blocks (ECC blocks). Each ECC block consists of 16sectors. These two ECC blocks (32 sectors) are generated by appendingscramble data. Upon playing back the reference code appended with thescramble data, filter operation or the like on the playback side is doneto play back a specific data symbol (e.g., 172), thus assuring data readprecision after that.

[0123] The control data in lead-in area 27 is made up of 192 ECC blocks.This control data field repetitively records the contents for 16 sectorsin each block 192 times.

[0124] This control data made up of 16 sectors contains physical formatinformation in the first sector (2,048 bytes), and disc manufacturinginformation and contents provider information in the subsequent sectors.

[0125] The physical format information contained in the control dataincludes the following contents.

[0126] That is, the First position describes the version of the DVDformat that the recorded information complies with.

[0127] The second position describes the size (12 cm, 8 cm, or the like)of a recording medium (optical disc 10) and minimum read-out rate. Incase of a read-only DVD video, 2.52 Mbps, 5.04 Mbps, and 10.08 Mbps areprescribed minimum read-out rates, but other minimum read-out rates arereserved. For example, when an RTR video recorder capable of variablebit rate recording records at an average bit rate of 2 Mbps, the minimumread-out rate can be set to fall within the range from 1.5 to 1.8 Mbpsusing the reserve field.

[0128] The third position describes the disc structure (the number ofrecording layers, track pitch, recording layer type, and the like) ofthe recording medium (optical disc 10). Based on this recording layertype, disc 10 can be identified to be a DVD-ROM, DVD-R, or DVD-RAM (orDVD-RW).

[0129] The fourth position describes the recording density (lineardensity and track density) of the recording medium (optical disc 10).The linear density indicates the recording length per bit (0.267 μm/bit,0.293 μm/bit, or the like). On the other hand, the track densityindicates the neighboring track spacing (0.74 μm/track, 0.80 μm/track,or the like). The fourth position also includes a reserve field todesignate other numerical values as the linear density and track densityof a DVD-RAM or DVD-R.

[0130] The fifth position describes the start and end sector numbers andthe like of data area (volume space) 28 of the recording medium (opticaldisc 10).

[0131] The sixth position describes a burst cutting area (BCA)descriptor. This BCA is applied as an option to a DVD-ROM disc alone,and is an area for storing recorded information upon completion of thedisc manufacturing process.

[0132] The seventh position describes a free space size of the recordingmedium (optical disc 10). For example, when disc 10 is a single-sidedsingle-layered recording DVD-RAM disc, information indicating 2.6 GB (orthe number of sectors corresponding to this number of bytes) is storedat that position of disc 10. On the other hand, when disc 10 is adouble-sided recording DVD-RAM disc, information indicating 5.2 GB (orthe number of sectors corresponding to this number of bytes) is storedat that position.

[0133] Other positions are reserved for future use.

[0134]FIG. 3 is a view for explaining the data structure of the videoobject shown in FIG. 2.

[0135] As shown in FIG. 3, each cell (for example, cell #m) consists ofone or more video object units (VOBUs). Each VOBU is constituted as aset (pack sequence) of video packs, sub-picture packs, audio packs,dummy packs, and the like.

[0136] Each of these packs has a predetermined size (2,048 bytes) andserves as a minimum unit for data transfer. The minimum unit for logicalprocessing is a cell, and logical processing is done is units of cells.

[0137] The playback or presentation time of the VOBU corresponds to thatof video data made up of one or more picture groups (groups of pictures;to be abbreviated as GOPs) included in the VOBU, and is set to fallwithin the range from 0.4 sec to 1.2 sec. One GOP is screen data whichnormally has a presentation time of about 0.5 sec in the MPEG format,and is compressed to play back approximately 15 frame images during thisinterval. (The VOBU includes an integer number of GOPs except for aspecial case wherein a gap is produced in the video data flow. That is,the VOBU is normally a video information compression unit synchronouswith GOPs.)

[0138] When the VOBU includes video data, a video datastream is formedby arranging GOPs (complying with MPEG) each consisting of video packs,sub-picture packs, audio packs, and the like. However, independently ofthe number of GOPS, the VOBU is defined with reference to thepresentation time of GOPs.

[0139] Note that even playback data consisting of audio data and/orsub-picture data alone is formed using the VOBU as one unit. Forexample, when the VOBU is formed by audio packs alone, audio packs to beplayed back in the presentation time of the VOBU to which the audio databelong are stored in that VOBU as in the video object of video data.

[0140] The packs that form each VOBU have similar data structures exceptfor a dummy pack. An audio pack will be taken as an example. As shown inFIG. 3, a pack header is allocated at the beginning of the pack, apacket header and sub-stream ID follow, and audio data is allocated atthe end of the pack. In such pack format, the packet header is writtenwith information of presentation time stamp PTS indicating the starttime of the first frame in the packet.

[0141] Likewise, a pack that stores real-time recording data can be madeup of a pack header, a packet header that can contain PTS informationand stuffing bytes as needed, and a data area that stores video, audio,sub-picture, or real-time recording data. At the end of this data area,padding bytes can be appended as needed.

[0142] The pack header can contain data such as a pack start code,system clock reference (SCR), program multiplex rate, pack stuffinglength, and the like.

[0143] In a DVD-RTR recorder/player that can record a video program thatcontains video object DA22 with the structure shown in FIG. 3 on opticaldisc 10, the user often wants to edit the recording contents afterrecording. In order to meet such requirement, dummy packs can beappropriately inserted in each VOBU. Each dummy pack can be used torecord edit data later.

[0144] The dummy pack shown in FIG. 3 has a data structure shown in FIG.4. More specifically, one dummy pack 89 is comprised of pack header 891,packet header 892 having a predetermined stream ID, and padding data 893padded with a predetermined code (insignificant data). Note that packetheader 892 and padding data 893 form padding packet 890. The contents ofpadding data 893 in a non-used dummy pack are not especiallysignificant.

[0145] This dummy pack 89 can be used as needed when the recordingcontents are to be edited after predetermined image recording is done ondisc 10 shown in FIG. 1, and in other cases.

[0146] More specifically, the dummy pack is inserted into each VOBU forthe purposes of:

[0147] addition of information to be additionally recorded after imagerecording (for example, memo information indicating that after-recordinginformation is inserted into an audio pack and replaced by a dummy packis inserted as sub-picture information into a sub-picture pack and isreplaced by a dummy pack);

[0148] compensation of a short size from an integer multiple of 32kbytes to match the VOBU size with an integer multiple of the ECC blocksize (32 kbytes); and so forth.

[0149] Also, the dummy pack can be used to store reduced-scale image(thumbnail picture) data which is displayed on a user menu, as needed.

[0150]FIG. 5 is a view for explaining an example of the directorystructure of information (data files) recorded on the optical disc shownin FIG. 1 to have the data structure shown in FIG. 2.

[0151] According to the DVD-RTR specification capable of digitalreal-time recording/playback of a video picture, the contents of a DVDdisc are managed using the directory structure shown in FIG. 5, and aresaved in accordance with a file system such as ISO9660, UDF, or thelike.

[0152] Even when the data structure shown in FIG. 2 is used on thedisc/apparatus side, this data structure is invisible to the user. Thedata structure that the user can actually see is a hierarchical filestructure shown in FIG. 5.

[0153] More specifically, directories such as a DVD_RTR directory,VIDEO_TS directory, AUDIO_TS directory, computer data file directory,and the like are displayed on the display screen (not shown) of the rootdirectory by means of menu windows, icons, or the like in correspondencewith the types of data recorded on data area DA shown in FIG. 2.

[0154] The DVD_RTR directory shown in FIG. 5 stores file RTR.IFO ofnavigation data RTR_VMG, file RTR_MOV.VRO/VR_MOVIE.VRO of movie videoobject RTR_MOV.VOB, file RTR_STO.VRO/VR_STILL.VRO of still picture videoobject RTR_STO.VOB, file RTR_STA.VRO/VR_AUDIO.VRO of still pictureadditional audio object RTR_STA.VOB for still pictures, and the like.

[0155] Note that file RTR.IFO stores management information such as aprogram set, program, entry point, play list, and the like for managingmoving picture information.

[0156] File RTR_MOV.VRO/VR_MOVIE.VRO stores recorded moving pictureinformation and its audio information, file RTR_STO.VRO/VR_STILL.VROstores recorded still picture information and its audio information, andfile RTR_STA.VRO/VR_AUDIO.VRO stores after-recording data for a stillpicture, and the like.

[0157] When a DVD-RTR recorder/player (RTR video recorder) has afunction of displaying the directories shown in FIG. 5 and also has aplayback function of a DVD video disc (ROM disc), and the DVD video discis set in its disc drive, the VIDEO_TS directory shown in FIG. 5 isactivated. In this case, when the VIDEO_TS directory is opened, therecorded contents of the set disc are further displayed.

[0158] When the DVD-RTR recorder/player has a DVD audio playbackfunction and a DVD audio disc is set in its disc drive, the AUDIO_TSdirectory shown in FIG. 5 is activated. In this case, when the AUDIO_TSdirectory is opened, the recorded contents of the set disc are furtherdisplayed.

[0159] Furthermore, when the DVD-RTR recorder/player comprises apersonal computer with a DVD-RAM drive and has a computer dataprocessing function, and a DVD-RAM (or DVD-ROM) disc that has recordedcomputer data is set in that disc drive, the computer data directoryshown in FIG. 5 is activated. In this case, when the computer datadirectory is opened, the recorded contents of the set disc are furtherdisplayed.

[0160] The user can access the recorded sources of DVD video, DVD videoROM, DVD audio, and computer data (including computer programs) as if heor she were operating a personal computer, while observing a menu screenor window display screen displayed with the directory structure shown inFIG. 5.

[0161]FIG. 6 is a view for explaining the data structure of thenavigation data file (RTR_VMG) shown in FIG. 5. RTR video managerRTR_VMG as navigation data is comprised of various kinds of information,as shown in FIG. 6.

[0162] Referring to FIG. 6, RTR video manager information RTR_VMGIdescribes basic information of recordable/reproducible optical disc (RTRdisc) 10 shown in FIG. 1. This RTR_VMGI contains video managerinformation management table VMGI_MAT and play list search pointer tablePL_SRPT.

[0163] RTR_VMGI further contains movie AV file information tableM_AVFIT, still picture AV file information table S_AVFIT, original PGCinformation ORG_PGCI, user defined PGC information table UD_PGCIT, textdata manager TXTDT_MG, and manufacturer's information table MNFIT.

[0164]FIG. 7 shows the contents of the video manager informationmanagement table (VMGI_MAT) shown in FIG. 6.

[0165] Referring to FIG. 7, VMG identifier VMG_ID describes“DVD_RTR_VMG0” that specifies an RTR_VMG file using an ISO646 characterset code.

[0166] RTR_VMG_EA describes the end address of RTR_VMG by a relativebyte number from the first byte of RTR_VMG.

[0167] VMGI_EA describes the end address of RTR_VMGI by a relative bytenumber from the first byte of RTR_VMG.

[0168] VERN describes the version number of the DVD specification forvideo recording (real-time video recording).

[0169] TM_ZONE describes the time zone of the RTR disc. In the DVD_RTRspecification, five different data fields (PL_CREATE_TM, VOB_REC_TM,FIRST_VOB_REC_TM, LAST_VOB_REC_TM, and VOBU_REC_TM) are specified. Thesefive different data fields are generally called REC_TM. REC_TM containsdata TZ_TY and TZ_OFFSET. TZ_TY describes a common universal time orlocal time, and TZ_OFFSET describes a date offset from the commonuniversal time in units of minutes.

[0170] STILL_TM describes the still time of a still picture in units ofseconds.

[0171] CHRS describes a character set code used in primary textinformation. With this CHRS, for example, an ISO8859-1 character setcode or shift JIS kanji code can be designated.

[0172] RSM_MRKI describes program chain number PGCN, program number PGN,cell number CN, marker point MRK_PT, and marker creation time MRK_TM.PGCN in this information indicates the number of the program chain wherea marker point is present. When a marker is present in an original PGC,PGCN is set at “0”. PGN indicates the number of the program where themarker point is present. When a resume marker is present in a userdefined PGC, PGN is set at “0”. CN indicates the number of a cell wherethe marker point is present. MRK_PT indicates a marker point in a targetcell. When the resume marker is present in a movie cell, MRK_PTdescribes a presentation time (PTM) using an RTR presentation timedescription format. MRK_TM describes the time of creation of the markerusing an RTR date description format.

[0173] REP_PICTI describes program chain number PGCN, program numberPGN, cell number CN, picture point PICT_PT, and representative picturecreation time CREAT_TM of the disc.

[0174] PGCN in this information indicates the number of the programchain where a representative picture of the disc is present. Therepresentative picture of the disc is designated by only the pointer inan original PGC. Hence, when this representative picture pointer ispresent, PGCN is set at “0”. PGN indicates the number of the programwhere the representative picture of the disc is present. When a resumemarker is present in a user defined PGC, PGN is set at “0”. CN indicatesthe number of a cell where the representative picture of the disc ispresent. PICT_PT indicates the representative picture of the disc in thetarget cell. When the representative picture is present in a movie cell,PICT_PT describes the presentation time (PTM) using the RTR presentationtime description format. When this representative picture is present ina still picture cell, PICT_PT describes a still picture VOB entry number(S_VOB_ENTN) in a corresponding still picture VOB group (S_VOG).CREAT_TM describes the time of creation of the representative picture ofthe disc using the RTR date description format.

[0175] M_AVFIT_SA describes the start address of movie AV fileinformation table M_AVFIT shown in FIG. 6 by a relative byte number fromthe first byte of RTR_VMG.

[0176] S_AVFIT_SA describes the start address of still picture AV fileinformation table S_AVFIT shown in FIG. 6 by a relative byte number fromthe first byte of RTR_VMG.

[0177] ORG_PGCI_SA describes the start address of original PGCinformation ORG_PGCI shown in FIG. 6 by a relative byte number from thefirst byte of RTR_VMG.

[0178] UD_PGCIT_SA describes the start address of user defined PGCinformation table UD_PGCIT shown in FIG. 6 by a relative byte numberfrom the first byte of RTR_VMG. If UD_PGCIT is not available,UD_PGCIT_SA is set at “0000 0000h”.

[0179] TXTDT_MG_SA describes the start address of text data manager.TXTDT_MG shown in FIG. 6 by a relative byte number from the first byteof RTR_VMG. If TXTDT_MG is not available, TXTDT_MG_SA is set at “00000000h”.

[0180] MNFIT_SA describes the start address of manufacturer'sinformation table MNFIT shown in FIG. 6 by a relative byte number fromthe first byte of RTR_VMG. If MNFIT is not available, MNFIT_SA is set at“0000 0000h”.

[0181]FIG. 8 shows the data structure of play list search pointer tablePL_SRPT shown in FIG. 6.

[0182] PL_SRPT describes information required for searching andaccessing play lists in an RTR disc, and contains play list searchpointer table information PL_SRPTI and one or more play list searchpointers PL_SRP#1 to PL_SRP#n.

[0183] Each play list is made up of a user defined PGC, and each PL_SRPhas a PGC number corresponding to that play list.

[0184] Each play list is specified by play list number PLN assignedthereto. PLNs are assigned to all pointers PL_SRP, and have serialnumbers from 1 to 99 (maximum) in the order of one or more pointersPL_SRP described in PL_SRPT.

[0185] The user can identify a specific play list from other ones usingPLN. Or the user can identify a specific play list from other ones usingtext information appended to the play list.

[0186]FIG. 9 shows the contents of play list search pointer tableinformation PL_SRPTI shown in FIG. 8.

[0187] PL_SRP_Ns indicates the number of play list search pointersPL_SRP in PL_SRPT.

[0188] PL_SRPT_EA indicates the end address of play list search pointertable PL_SRPT, which is described by a relative byte number from thefirst byte of PL_SRPT.

[0189]FIG. 10 shows the contents of play list search pointer PL_SRPshown in FIG. 8.

[0190] Referring to FIG. 10, PL_TY describes the play list type. Thatis, one of movie, still picture, or hybrid (both movie and stillpicture) play lists can be specified by the contents (4-byte PL_TY1) ofPL_TY.

[0191] PGCN describes the number of corresponding user defined programchain UD_PGC. The maximum value of this PGCN is 99.

[0192] PL_CREATE_TM describes the time of creation of the play listusing the RTR date description format. This PL_CREATE_TM can describeyear, month, day, hour, minute, and second.

[0193] PRM_TXTI describes primary text information of the play list.This PRM_TXTI consists of 128 bytes, the first 64 bytes of which areused to describe primary text information using ASCII character sets,and the remaining 64 bytes of which are used to describe primary textinformation using other character sets (shift JIS, ISO8859-15, and thelike). Other character set codes are described in VMGI_MAT, and can beused by all pieces of primary text information in the disc. Note that aterminal control code is not described in PRM_TXTI.

[0194] IT_TXT_SRPN describes the number of IT_TXT_SRP of the play list.(Item text IT_TXT will be described later with reference to FIG. 18.)

[0195] THM_PTRI describes information of thumbnail pointer THM_PTR.Thumbnail pointer information THM_PTRI may be optionally set or used ineither an RTR recorder and player. If the RTR recorder does not haveperformance capable of processing THM_PTRI, all pieces of 8-byteTHM_PTRI can be set at “FFh”. If the RTR player does not haveperformance capable of processing THM_PTRI, it may simply ignoreTHM_PTRI.

[0196] Note that a “thumbnail” means a picture as small as the nail ofthe thumb, and normally indicates a picture which is obtained byreducing a still picture in a recorded video picture to the thumbnailsize.

[0197]FIG. 11 shows the contents of thumbnail pointer informationTHM_PTRI shown in FIG. 10. Referring to FIG. 11, CN describes the numberof a cell where the thumbnail point is present. Also, THM_PT describesthe thumbnail point in a target cell.

[0198] When the resume marker is present in a movie cell, THM_PTdescribes the presentation time (PTM) using the RTR presentation timedescription format.

[0199] When a thumbnail is present in a still picture cell, THM_PTdescribes a still picture VOB entry number (S_VOB_ENTN) in acorresponding still picture VOB group (S_VOG).

[0200]FIG. 12 shows the data structure of the movie AV file informationtable (M_AVFIT) shown in FIG. 6.

[0201] M_AVFIT describes information of a movie AV file (fileRTR_MOV.VRO/VR_MOVIE.VRO shown in FIG. 5), and contains movie AV fileinformation table information M_AVFITI, one or more pieces of movie VOBstream information M_VOB_STI#1 to M_VOB_STI#n, and movie AV fileinformation M_AVFI.

[0202] M_AVFI is information of a movie AV file having a predeterminedfile name (RTR_MOV.VRO/VR_MOVIE.VRO), and contains movie AV fileinformation general information M_AVFI_GI, one or more movie VOBinformation search pointers M_VOBI_SRP#1 to M_VOBI_SRP#n, and one ormore pieces of movie VOB information M_VOBI#1 to M-VOBI#n.

[0203] One movie AV file can contain one or more VOBS, and each VOB hasmovie VOB information M_VOBI for VOB in M_AVFI. One or more pieces ofinformation M_VOBI in M_AVFI are described in the same order as that ofVOB data stored in the movie AV file.

[0204]FIG. 13 shows the data structure of the movie VOB informationM_VOBI shown in FIG. 12. As shown in FIG. 13, M_VOBI contains movie VOBgeneral information M_VOBI_GI, seamless information SMLI, audio gapinformation AGAPI, and time map information TMAPI.

[0205] M_VOBI_GI shown in FIG. 13 contains VOB TY which describes thetype of VOB, VOB_REC_TM which describes the recording time of the startfield in VOB using the RTR date description format, VOB_REC_TM_SUB whichdescribes the recording time (sub-second information) of the start fieldin VOB by the number of video fields, M_VOB_STIN which describes thenumber of movie VOB stream information, VOB_V_S_PTM which describes thepresentation start time of the first video field in VOB using the RTRpresentation time description format, and VOB_V_E_PTM which describesthe presentation end time of the last video field in the VOB using theRTR presentation time description format.

[0206] VOB_TY includes TE which indicates if that VOB has beentemporarily erased, A0_STATUS which indicates the status of audio stream#0, A1_STATUS which indicates the status of audio stream #1, analogprotection system APS which indicates the format of analog copyprotection or the ON/OFF state of this copy protection, SML_FLG whichindicates if VOB is to be played back seamlessly, A0_GAP_LOC whichindicates if an audio gap is present in audio stream #0 and the locationof the audio gap if it is present, and A1_GAP_LOC which indicates if anaudio gap is present in audio stream #1 and the location of the audiogap if it is present.

[0207] VOB_REC_TM is updated to indicate the recording time of the startfield of the remaining VOB if the start field of a given VOB is deleted(erased).

[0208] More specifically, “new VOB_REC_TM=old VOB_REC_TM + presentationduration of deleted field”.

[0209] On the other hand, if the presentation duration of the deletedfield cannot be displayed in units of seconds (for example, when thepresentation duration of the deleted field is 60.5 sec),

[0210] “new VOB_REC_TM+new VOB_REC_TM_SUB=old VOB_REC_TM +oldVOB_REC_TM_SUB + presentation duration of deleted field”.

[0211] Since VOB_REC_TM describes the date of video recording, even whenaudio data has been modified, such modification has no influence onVOB_REC_TM.

[0212] The aforementioned RTR date description format will be brieflyexplained below. In this format, presentation time PTM is expressed by aPTM base and PTM extension. The PTM base is a value measured using 90kHz as a unit, and the PTM extension is a value measured using 27 MHz asa unit.

[0213] SMLI shown in FIG. 13 contains VOB_FIRST_SCR which describes SCR(system clock reference) of the first pack of current VOB using the RTRpresentation time description format, and PREV_VOB_LAST_SCR whichdescribes SCR of the last pack in previous VOB using the RTRpresentation time description format.

[0214]FIG. 14 shows the data structure of the time map information TMAPIshown in FIG. 13. Time map information TMAPI is used upon executingspecial playback (e.g., cell playback in an order unique to each userusing a user defined PGC) and time search.

[0215] Time map information TMAPI includes time map general informationTMAP_GI, one or more time entries TM_ENT#1 to TM_ENT#r, and one or moreVOBU entries VOBU_ENT#1 to VOBU_ENT#q.

[0216] Each VOBU entry contains information of the size and presentationtime of VOBU. The VOBU size is presented in units of sectors (2 kbytes),and the presentation time is presented in units of video fields (onefield={fraction (1/60)} sec in NTSC; one field={fraction (1/50)} sec inPAL).

[0217] Since the VOBU size is presented in units of sectors, asdescribed above, VOBU can be accessed using addresses in units ofsectors.

[0218] Each VOBU entry includes reference picture size information1STREF_SZ, VOBU playback time information VOBU_PB_TM, and VOBU sizeinformation VOBU_SZ.

[0219] Note that VOBU_PB_TM represents the playback time of VOBU ofinterest in units of video fields. On the other hand, reference picturesize information 1STREF_SZ represents the size of the first referencepicture (corresponding to I-picture in MPEG) of VOBU of interest inunits of sectors.

[0220] On the other hand, each time entry contains address information(VOBU_ADR) of the corresponding VOBU, and time difference information(TM_DIFF). This time difference information indicates the differencebetween the playback time designated by the time entry and the VOBUpresentation start time.

[0221] Assuming that the time interval (time unit TMU) between twosuccessive time entries is 10 sec, this time entry interval correspondsto 600 fields in, e.g., NTSC video.

[0222] Normally, the “time interval between neighboring VOBUs” isexpressed by the number of fields in the VOBU entry. As another method,a “count value from a given VOBU to the next VOBU by a clock counter”may be used to express the “time interval between neighboring VOBUs”.

[0223] For example, the “time interval between neighboring VOBUs” can beexpressed by the “difference value between the value of presentationtime stamp at the start position of one VOBU and the value of PTS at thestart position of the immediately succeeding VOBU”.

[0224] In other words, “the time interval in a specific unit can beexpressed by the difference value of the clock counter in that unit”.

[0225]FIG. 15 shows the contents of time map general information TMAP_GIshown in FIG. 14.

[0226] This time map general information TMAP_GI includes TM_ENT Nsindicating the number of time entries in that time map information,VOBU_ENT_Ns indicating the number of VOBU entries in that time mapinformation, time offset TM_OSF for that time map information, andaddress offset ADR_OFS of that time map information.

[0227] When a value (10 sec or equivalent) corresponding to 600 fieldsin NTSC video (or 500 fields in PAL video) is used as time unit TMU,time offset TM_OSF is used to represent the time offset within TMU.

[0228] When the VOBU size is expressed by the number of sectors, addressoffset ADR_OFS is used to indicate a file pointer from the beginning ofan AV file.

[0229]FIG. 16 shows the contents of time entry TM_ENT shown in FIG. 14.

[0230] This time entry TM_ENT includes VOBU_ENTN indicating the numberof the corresponding VOBU entry, TM_DIFF indicating the time differencebetween the presentation start time of VOBU designated by the timeentry, and the calculated presentation time, and VOBU_ADR indicating thetarget VOBU address.

[0231] When time unit TMU is expressed by 600 fields in NTSC (or whentime unit TMU is expressed by 500 fields in PAL), the “calculatedpresentation time” with respect to time entry #j is given by TMU(j−1)+TM_OSF.

[0232] On the other hand, VOBU_ADR indicates the target VOBU address bythe total size of VOBUS preceding VOBU of interest when the VOBU size isexpressed in units of sectors.

[0233] In the aforementioned data structure, in order to startpresentation from the middle of a certain VOBU, that access point mustbe determined. This access point is assumed to be a time entry point.

[0234] This time entry point is located at a position separated from theposition indicated by movie address information of VOBU by the timedifference indicated by time difference information TM_DIFF in timeentry TM_ENT. This time entry point serves as a special presentationstart point (or time search point) indicated by time map informationTMAPI.

[0235]FIG. 17 shows the data structure of user defined PGC informationtable UD_PGCIT shown in FIG. 6.

[0236] UD_PGCIT includes user defined PGC information table informationUD_PGCITI, one or more user defined PGCI search pointers UD_PGCI_SRP#1to UD_PGCI_SRP#n, and one or more pieces of user defined PGC informationUD_PGCI#1 to UD PGCI#n.

[0237] All UD_PGCs are assigned program chain numbers PGCN ranging from1 to 99 in the description order of UD_PGCI_SRP in UD_PGCIT. This PGCNcan specify each PGC.

[0238] UD_PGCITI contains UD_PGCI_SRP_Ns indicating the number ofUD_PGCI_SRPS, and UD_PGCIT_EA indicating the end address of UD_PGCIT.

[0239] Note that the maximum value of UD_PGCI_SRP_Ns is set at, e.g.,“99”. UD_PGCIT_EA represents the end address of UD_PGCIT by a relativebyte number from the first byte of UD_PGCIT.

[0240] UD_PGCI_SRP includes start address UD_PGCI_SA of UD_PGCI. ThisUD_PGCI_SA represents the start address of UD_PGCI by a relative bytenumber from the first byte of UD_PGCIT.

[0241]FIG. 18 shows the data structure of text data manager TXTDT_MGshown in FIG. 6.

[0242] TXTDT_MG contains text data information TXTDTI, one or more itemtext search pointers IT_TXT_SRP#1 to IT_TXT_SRP#n, and one or more itemtexts IT_TXT.

[0243] TXTDTI includes CHRS that describes a character set code(ISO8859-1 or shift JIS kanji) used in TXTDT_MG, IT_TXT_SRP_Ns thatdescribes the number of pointers IT_TXT_SRP, and TXTDT_MG_EA thatdescribes the end address of TXTDT_MG by a relative byte number from thefirst byte of TXTDT_MG.

[0244] Each IT_TXT_SRP includes IT_TXT_SA that describes the startaddress of IT_TXT by a relative byte number from the first byte ofTXTDT_MG.

[0245] IT_TXT describes item text by a character code designated byCHRS. The data length (the number of bytes) of IT_TXT changes dependingon the text contents.

[0246]FIG. 19 shows the data structure of the PGC information PGCI(information of an original PGC or user defined PGC).

[0247] PGCI contains navigation information for program chain PGC.

[0248] Two different types of program chains, i.e., an original PGC anduser defined PGC, are available (see the contents of RTR_VMG shown inFIG. 6). The original PGC has VOB and PGCI. However, the user definedPGC does not have its own VOB, and refers to VOB in the original PGC.

[0249] As shown in FIG. 19, PGC information (PGCI#i) includes PGCgeneral information PGC_GI, one or more pieces of program informationPGI#1 to PGI#m, one or more cell information search pointers CI_SRP#1 toCI_SRP#n, and one or more pieces of cell information CI#1 to CI#n.

[0250] Note that the start address of cell information CI can beindicated by CI_SA described by a relative byte number from the firstbyte of PGCI.

[0251]FIG. 20 shows the contents of PGC general information PGC_GI shownin FIG. 19.

[0252] This PGC_GI contains PG_Ns that describes the number of programsin PGC, and CI_SRP_Ns that describes the number of CI_SRPs in PGC.

[0253] In case of the user defined PGC, PG_Ns is set at “0”. On theother hand, the maximum number of programs PG in the original PGC is“99”, and the maximum number of cells in the PGC is “999”.

[0254]FIG. 21 shows the contents of program information PGI shown inFIG. 19.

[0255] This PGI includes PG TY which describes the type of program, C_Nswhich describes the number of cells in PG, primary text informationPRM_TXTI used in PG, search pointer number IT_TXT_SRPTN of IT_TXT wheretext data corresponds to PG, and thumbnail pointer information THM_PTRI.

[0256] Note that PRM_TXTI is constructed by a 128-byte field, and thefirst 64 bytes of that field are described by an ASCII character set.When ASCIT text is less than 64 bytes, “00h” is written in blank bytes.

[0257] The second 64 bytes of the 128-byte field are used to describeprimary text of another character set (e.g., shift JIS or ISO8859-15).Note that the code of “another character set” is described in VMGI_MAT,and is shared by all the pieces of primary text information in the disc.

[0258] Note that a terminal control code that assumes a value rangingfrom “01h” to “1Fh” is never described in PRM_TXTI.

[0259] THM_PTRI describes information of a thumbnail pointer. That is,THM_PTRI includes CN that describes the number of the cell where thethumbnail pointer is present, and THM_PT that describes the thumbnailpoint in the target cell.

[0260] When the resume marker is present in a movie cell, THM_PTdescribes the presentation time (PTM) using the RTR presentation timedescription format.

[0261] On the other hand, when a thumbnail is present in a still picturecell, THM_PT describes a still picture VOB entry number (S_VOB_ENTN) ina corresponding still picture VOB group (S_VOG).

[0262] THM_PTRI may be optionally set or used in either an RTR recorderor player. When the RTR recorder does not have performance capable ofprocessing THM_PTRI, all the pieces of 8-byte THM_PTRI may be set at“FFh”. On the other hand, when the RTR player does not have performancecapable of processing THM_PTRI, it may simply ignore THM_PTRI.

[0263]FIG. 22 shows the data structure of cell information CI shown inFIG. 19. As shown in FIG. 22, there are two kinds of cell information,i.e., movie cell information M_CI and still picture cell informationS_CI.

[0264] Information (M_C_EPI) that pertains to the entry point is writtenin movie cell information M_CI in navigation data file RTR.IFO shown inFIG. 5.

[0265]FIG. 23 shows the data structure of movie cell information M_CIshown in FIG. 22. As shown in FIG. 23, M_CI contains movie cell generalinformation M_C_GI, and one or more pieces of movie cell entry pointinformation M_C_EPI#1 to M_C_EPI#n.

[0266]FIG. 24 shows the contents of movie cell general informationM_C_GI shown in FIG. 23.

[0267] That is, M_C_GI contains C_TY which describes the type of cell,M_VOBI_SRPN which describes the number of the movie VOBI search pointercorresponding to VOB of this cell, C_EPI_Ns which describes the numberof pieces of cell entry point information, C_V_S_PTM which describes thepresentation start time of this cell using the RTR presentation timedescription format, and C_V_E_PTM which describes the presentation endtime of this cell using the RTR presentation time description format.

[0268] Note that C_V_S_PTM and C_V_E_PTM satisfy the followingconditions.

[0269] (1) In case of cell in original PGC C_V_S_PTM must be set in thefirst four VOBUs of the corresponding VOB; and

[0270] C_V_S_PTM must be set in the last four VOBUs of the correspondingVOB.

[0271] (2) In case of cell in user defined PGCO_C_V_S_PTM≦C_V_S_PTM≦C_V_E_PTM≦O_C_V_E_PTM must hold,

[0272] where O_C_V_S_PTM indicates the presentation start time of anoriginal cell corresponding to VOB referred to by this cell, andO_C_V_E_PTM indicates the presentation end time of an original cellcorresponding to VOB referred to by this cell.

[0273]FIG. 25 shows the contents of movie cell entry point informationM_C_EPI shown in FIG. 23.

[0274] This M_C_EPI has two types (type 1 and type 2). M_C_EPI of type 1without any text information is composed of EP_TY and EP_PTM, andM_C_EPI of type 2 with text information is composed of EP_TY, EP_PTM,and PRM_TXTI. FIG. 25 shows M_C_EPI of type 2.

[0275] As shown in FIG. 25, M_C_EPI includes EP_TY that describes thetype of entry point, EP_PTM that describes the presentation time of theentry point using the RTR presentation time format, and PRM_TXTI thatdescribes primary text information and the like of the entry point.

[0276] Upon playback, the value EP_PTM and cell playback time areconverted into file pointers that point to VOBU by the time map TMAPinformation (see FIGS. 14 to 16), and are also converted into physicaladdresses by the file system.

[0277] PRM_TXTI in M_C_EPI is constructed by a 128-byte field. The first64 bytes of that field are used to describe primary text using an ASCIIcharacter set. When ASCII text is less than 64 bytes, “00h” fills blankbytes. The latter 64 bytes of the 128-byte field are used to describeprimary text of another character set (e.g., shift JIS, ISO8859-15, orthe like). Note that “another character set” is described in VMGI_MAT,and is shared by all the pieces of primary text information in the disc.

[0278] Note that a terminal control code that assumes a value rangingfrom “01h” to “1Fh” is never described in PRM_TXTI.

[0279] EP_TY in M_C_EPI is comprised of 1-byte data including a 2-bittype identification code. If this identification code is “00b”, itindicates that M_C_EPI is of type 1 (empty primary text data or nodata); if the code is “01b”, it indicates that M_C_EPI is of type 2(primary text data).

[0280] This EP_TY has a 6-bit reserved field in addition to the 2-bittype identification code that identifies type 1 or 2. Using some or allthe bits of this reserved field, the contents of PRM_TXTI in M_C_EPI canbe further specified. (If all the six bits are used, a maximum of 64different specifications may be made. More than 6 bits may be assignedto this designation code to specify more types.)

[0281] The bits using this reserved field will be referred to as adesignation code for designating the contents of the primary textinformation hereinafter.

[0282] Specific bits in the designation code can designate whetherPRM_TXTI in M_C_EPI shown in FIG. 25 is “text information” with“information type” and/or “information date” or “text information”without “information type” and/or “information date”.

[0283] Furthermore, specific bits in the designation code can designatewhether PRM_TXTI in M_C_EPI shown in FIG. 25 is “text information” withcorresponding “thumbnail information” in addition to “information type”and/or “information date”, or “text information” without “thumbnailinformation”. (The “thumbnail information” corresponds to, e.g.,thumbnail pointer information THM_PTRI shown in FIG. 21.)

[0284] Moreover, specific bits in the designation code can designatewhether PRM_TXTI in M_C_EPI shown in FIG. 25 consists of “thumbnailinformation” alone without any “text information” or “thumbnailinformation” with “text information”.

[0285] When the designation code (not shown) in EP_TY designates“information type”, “information date”, and “text information” shown inFIG. 25, these pieces of information can be used to express thefollowing contents.

[0286] More specifically, “information type” describes an attribute ofthe entry point, “information date” describes the date the entry pointwas entered (recorded on the disc), and “text information” describesadditional information (a brief comment of a picture at the entry point)that pertains to the entry point.

[0287] The attributes of the entry point described in “information type”include:

[0288] information type [1]=0, user mark (the user enters an entrypoint)

[0289] information type [1]=1; set mark (the recorder/player enters anentry point)

[0290] information type [1]=2; defect start mark

[0291] information type [1]=3; defect end mark

[0292] information type [1]=4; presentation start mark

[0293] information type [1]=5; presentation end mark

[0294] information type [1]=6; erasure prohibition mark

[0295] information type [1]=7; another mark (e.g., an instruction fromother than the user or recorder/player).

[0296] Note that [1] in information type [1] means the first data fieldof the information type. If this data field has a 3-bit configuration,information type [1] can express eight different marks.

[0297] Note that information similar to “information type”, and“information date” and/or “text information” in FIG. 25 may be assuredin play list search pointer PL_SRP shown in FIG. 10.

[0298] The DVD-RTR system can process text information other than thetext managed by text data manager TXTDT_MG shown in FIG. 18. The textinformation includes primary text information (FIG. 21) described in aprogram, primary text information (FIG. 10) described in a play list,and primary text information (FIG. 25) described in the selected entrypoint.

[0299] The user uses such primary text information PRM_TXTI to identifythe corresponding recorded contents using a character set such as ASCII,shift JIS, or the like.

[0300]FIG. 26 shows that example. That is, the player (RTRrecorder/player) reads out primary text information PRM_TXTI shown inFIG. 21 from disc 10, and displays recording date information ofrecorded programs (PG1, PG2, PG3, . . .) on the display panel of theplayer (this example indicates that recording of program #1 was startedfrom PM 12:30:15).

[0301] When the corresponding primary text information PRM_TXTI is readout from the disc, the player outputs the result on a monitor(television). Before the beginning of playback of the recorded programs(PG1, PG2, PG3, . . .), brief comments (e.g., “barbecue with family” ofPG1, “7th birthday of daughter” of PG2, and the like) of the programsrecorded on that disc 10 are displayed on the monitor screen.

[0302] The user can easily select a desired program (e.g., “barbecuewith family) from this display. When the user has selected a desiredprogram by operating the cursors of a remote controller (not shown) andhas pressed a playback button, playback of program #1 is started.

[0303] Also, the user can similarly make display/user selection/playbackoperation using primary text information PRM_TXTI (FIG. 10) of a playlist, and those using primary text information PRM_TXTI (FIG. 25) of anentry point.

[0304] More specifically, as exemplified in FIG. 27, an entry point(corresponding to a “bookmark” compared to a book) can be set at anarbitrary position of each program, and text such as “barbecue withfamily” can be stored in primary text information PRM_TXTI (FIG. 25) ofthat entry point.

[0305] The same applies to a case wherein the user decomposes recordedprograms #1 to #4 into arbitrary parts, enters the playback order ofdecomposed parts in play lists #1 and #2, and sets entry points in theindividual parts.

[0306] Furthermore, a short title such as “barbecue with grandma” may bewritten in primary text information PRM_TXTI (FIG. 10) of each playlist.

[0307]FIG. 28 is a view for explaining a correspondence between thepresentation start times/presentation end times of cells that form auser defined PGC (or original PGC), and the offset addresses for VOBUSof VOBS that form movie video object RTR_MOV.VRO/VR_MOVIE.VRO shown inFIG. 5.

[0308] Referring to FIG. 28, information PGCI and information M_VOBI arestored in the RTR.IFO file shown in FIG. 5. A VOB as a set of VOBUScorresponding to a PGC as a set of cells is stored in theRTR_MOV.VRO/VR_MOVIE.VRO file shown in FIG. 5.

[0309] Program chain information PGCI of the original PGC shown in FIG.28 manages the playback method of a program as a set of one or morecells, and each user defined PGC manages the playback method of a set ofone or more cells determined by the user.

[0310] The presentation start time and presentation end time of eachcell in the original PGC or user defined PGC are converted by time mapinformation TMAPI contained in each M_VOBI#i shown in FIG. 13 into filepointers from the beginning of the VRO file, which point to a given VOBUthat stores the corresponding video data or the like, and are furtherconverted into physical addresses by the file system.

[0311] In order to play back each cell, the corresponding VOB number,presentation start time, and presentation end time are described as cellinformation. Upon playing back each cell, the presentation start and endtimes are passed on to the corresponding VOBI, are converted into filepointers that point to a VOBU corresponding to the cell playback timeusing a time map (TMAP) included in the VOBI, and are further convertedinto physical addresses by the file system, thus accessing a VOB.

[0312] For example, video data (VOBS) recorded in audio/video data areaDA2 in FIG. 2 is made up of a set of one or more program chains PGC.Each PGC is a set of programs as sets of one or more cells, and cells tobe played back and their order upon forming programs can be determinedby the original PGC information or user defined PGC information.

[0313] The playback times of cells and their playback order designatedby the original PGC information or user defined PGC information areconverted into VOBU addresses that form each of cells to be played backon the basis of the contents (time map TMAP shown in FIG. 28) of timemap information TMAPI shown in FIG. 14.

[0314] That is, upon playback based on the original PGC (the cellplayback order of the initially recorded state), the addresses of VOBUswithin the time band to be played back are obtained via time mapinformation (TMAP) in accordance with the contents of ORG_PGCI shown inFIG. 6, and playback is made in that order.

[0315] On the other hand, upon playback based on a PGC uniquely definedby the user (e.g., when the user has edited the playback order afterrecording), the addresses of VOBUs within the time band to be playedback are obtained via time map information (TMAP) in accordance with thecontents of UD_PGCI shown in FIG. 17, and playback is made in thatorder.

[0316] The cell playback order based on user defined PGC informationUD_PGCI can be quite different from that based on original PGCinformation ORG_PGCI.

[0317] The playback times and the addresses of VOBUs to be played backcan correspond to each other with reference to the contents of timeentries and VOBU entries in time map information TMAPI shown in FIG. 14.

[0318]FIG. 29 is a block diagram for explaining an example of thearrangement of an apparatus (RTR video recorder) for recording a videoprogram in real time and playing it back using recordable/reproducibleoptical disc 10 shown in FIG. 1.

[0319] The apparatus main body of the RTR video recorder shown in FIG.29 is roughly constructed by a disc drive unit (32, 34, and the like)for rotating DVD-RAM or DVD-R disc 10 and reading/writing information ondisc 10, encoder unit 50 which constructs the recording side, decoderunit 60 which constructs the playback side, and microcomputer block 30for controlling the operations of the overall apparatus.

[0320] Encoder unit 50 comprises ADC (analog-to-digital converter) 52,video encoder (V encoder) 53, audio encoder (A encoder) 54, sub-pictureencoder (SP encoder) 55, formatter 56, and buffer memory 57.

[0321] ADC 52 receives an external analog video signal+external analogaudio signal from AV input section 42, or analog TV signal+analog audiosignal from TV tuner 44, or the like. This ADC 52 converts the inputanalog video signal into digital data at, e.g., a samplingfrequency=13.5 MHz and the number of quantization bits=8.

[0322] Likewise, ADC 52 converts the input analog audio signal intodigital data at, e.g., a sampling frequency=48 kHz and the number ofquantization bits=16.

[0323] When an analog video signal and digital audio signal are input toADC 52, the digital audio signal passes through ADC 52.

[0324] On the other hand, when a digital video signal and digital audiosignal are input to ADC 52, these signals pass through ADC 52.

[0325] A digital video signal component from ADC 52 is supplied toformatter 56 via video encoder (V encoder) 53. Also, a digital audiosignal component from ADC 52 is supplied to formatter 56 via audioencoder (A encoder) 54.

[0326] V encoder 53 has a function of converting the input digital videosignal into a digital signal compressed at variable bit rate on thebasis of the MPEG2 or MPEG1 specifications.

[0327] A encoder 54 has a function of converting the input digital audiosignal into a digital signal (or linear PCM digital signal) compressedat fixed bit rate on the basis of the MPEG or AC-3 specifications.

[0328] When a DVD video signal is input from AV input section 42, orwhen a DVD video signal is broadcasted and is received by TV tuner 44, ateletext signal component in the DVD video signal is input to SP encoder55. Sub-picture data input to SP encoder 55 is arranged into apredetermined signal format, and is then sent to formatter 56.

[0329] Formatter 56 executes predetermined signal processing of theinput video signal, audio signal, sub-picture signal, and the like usingbuffer memory 57 as a work area, and outputs recording data that matchesa predetermined format (file structure) to data processor 36.

[0330] Standard encode process contents for generating the recordingdata will be briefly explained below. More specifically, when encoderunit 50 shown in FIG. 29 starts an encode process, parameters requiredfor encoding video data and the like are set. Main picture data ispre-encoded using the set parameters to compute optimal code amountdistribution for the selected average transfer rate (recording rate).Then, the main picture data is encoded based on the code amountdistribution obtained by pre-encoding. At this time, audio data isencoded simultaneously.

[0331] As a result of pre-encoding, if it is determined that the datacompression amount is insufficient (a desired video program cannot fallwithin a DVD-RAM disc or DVD-R disc to be used in recording), andpre-encoding can be re-done (if the source to be recorded is a sourcethat can be repetitively played back such as a video tape, video disc,or the like), main picture data is partially re-encoded, and thepreviously pre-encoded main picture data portion is replaced by there-encoded main picture data portion. With a series of processesdescribed above, the main picture and audio data are encoded, and theaverage bit rate value required for recording can be greatly reduced.

[0332] Analogously, parameters required for encoding sub-picture dataare set, and encoded sub-picture data is generated.

[0333] The encoded main picture, audio, and sub-picture data arecombined, and are converted into the DVD_RTR video structure.

[0334] The encoded main picture data, audio data, and sub-picture dataare segmented into packs each having a predetermined size (2,048 bytes),as shown in FIG. 3. Dummy packs are inserted into these packs, asneeded. Note that time stamps such as PTS (presentation time stamp), DTS(decode time stamp), and the like are described in packs other thandummy packs, as needed. As for PTS of sub-picture data, a timearbitrarily delayed from PTS of main picture data or audio data in theidentical playback time band can be described.

[0335] Data cells are arranged in units of VOBUs to allow playback inthe time code order of data, thus forming a VOB consisting of aplurality of cells. An RTR_MOV.VRO/VR_MOVIE.VRO file that combines oneor more VOBs is formatted into the structure shown in FIG. 5.

[0336] Upon digitally copying a DVD playback signal from the DVD videoplayer, since the contents of the cells, program chains, managementtables, time stamps, and the like are determined in advance, they neednot be created again. (However, upon designing the RTR video recorder tobe able to digitally copy a DVD playback signal, the recorder must havecopyright protection means such as digital watermarking means and thelike.)

[0337] The disc drive unit that reads/writes (records and/or plays back)information to/from DVD disc 10 comprises disc drive 32, temporarystorage buffer 34, data processor 36, and system time counter (or systemtime clock; STC) 38.

[0338] Temporary storage buffer 34 is used to buffer a given amount ofdata to be written on disc 10 (data output from encoder unit 50) viadisc drive 32, and to buffer a given amount of data played back fromdisc 10 (data input to decoder unit 60) via disc drive 32.

[0339] For example, when temporary storage buffer 34 comprises a 4-Mbytesemiconductor memory (DRAM), it can buffer recording or playback datafor approximately 8 seconds at an average recording rate of 4 Mbps. Whentemporary storage buffer 34 comprises a 16-Mbyte EEPROM (flash memory),it can buffer recording or playback data for approximately 30 seconds atan average recording rate of 4 Mbps. Furthermore, when temporary storagebuffer 34 comprises a 100-Mbyte, very small HDD (hard disc), it canbuffer recording or playback data for 3 minutes or more at an averagerecording rate of 4 Mbps.

[0340] Temporary storage buffer 34 can also be used to temporarily storerecording information when disc 10 is used up during recording, untilthat disc 10 is exchanged with a new disc.

[0341] When disc drive 32 uses a high-speed drive (a speed equal to orhigher than double speeds), temporary storage buffer 34 can also be usedto temporarily store readout data exceeding an amount read out from anormal drive per unit time. When temporary storage buffer 34 buffersreadout data upon playback, even when an optical pickup (not shown) hascaused read errors due to vibration shock or the like, playback databuffered by temporary storage buffer 34 can be used instead, thuspreventing the playback picture from being discontinued.

[0342] If an external card slot (not shown in FIG. 29) is provided tothe RTR video recorder, the EEPROM can be offered as an option IC card.On the other hand, if an external drive slot or SCSI interface isprovided to the RTR video recorder, the HDD can be offered as an optionextension drive.

[0343] When a personal computer is used as a DVD video recorder bysoftware (not shown), the free area of a hard disc drive or a mainmemory of the personal computer itself can be partially used astemporary storage buffer 34 shown in FIG. 29.

[0344] Data processor 36 in FIG. 29 supplies DVD_RTR recording data fromencoder unit 50 to disc drive 32, receives a DVD_RTR playback signalplayed back from disc 10, rewrites management information (some filedata in FIG. 5) recorded on disc 10, and deletes data (some or all offiles) recorded on disc 10, under the control of microcomputer block 30.

[0345] Microcomputer block 30 includes an MPU (or CPU), a ROM writtenwith control programs and the like, and a RAM which provides a work arearequired for executing programs.

[0346] The MPU of this microcomputer block 30 (to be also referred to asMPU 30 hereinafter) executes, using its RAM as a work area, an entrypoint enter process, text information input process, playback menudisplay process, text information search process (recorded contentsearch process), defect enter process, priority order of erasure enterprocess, and the like, in accordance with the control programs stored inits ROM.

[0347] In these processes, data (a text input of a short title of therecorded contents or the like) input by the RTR video recorder user issupplied from information input unit 100 to MPU 30. Information inputunit 100 can use a keyboard of a personal computer or cursorkeys/ten-key pad of a remote controller (not shown).

[0348] Of the execution results of MPU 30, the contents the user of theDVD_RTR video recorder should know are displayed on display unit 48 ofthe DVD_RTR video recorder. Such message contents are also displayed ona monitor display using on-screen display (OSD), sub-picture data, andthe like, as needed.

[0349] Note that the control timings of disc drive 32, data processor36, and encoder unit 50 and/or decoder unit 60 by MPU 30 can bedetermined based on time data supplied from STC 38 (videorecording/playback are normally executed in synchronism with time clocksfrom STC 38, but other processes may be executed at timingsindependently of STC 38).

[0350] Furthermore, MPU 30 can process the recorded dates of individualprograms recorded on disc 10, entered dates of entry points, and thelike on the basis of time data from timepiece unit 40.

[0351] Decoder unit 60 comprises separator 62 for separating andextracting the respective packs from DVD_RTR playback data with the packstructure shown in FIG. 3, memory 63 used upon executing pack separationand other signal processes, video decoder (V decoder) 64 for decodingmain picture data (the contents of video packs) separated by separator62, sub-picture decoder (SP decoder) 65 for decoding sub-picture data(the contents of sub-picture packs) separated by separator 62, audiodecoder (A decoder) 68 for decoding audio data (the contents of audiopacks) separated by separator 62, video processor 66 for appropriatelymixing sub-picture data from SP decoder 65 with video data output from Vdecoder 64 to superpose sub-picture data such as menus, highlightbuttons, superimposed dialogs, and the like on main picture data, andoutputting them, video digital-to-analog converter (V.DAC) 67 forconverting the digital video output from video processor 66 into ananalog video signal, and audio digital-to-analog converter (A.DAC) 69for converting the digital audio output from A decoder 68 into an analogaudio signal.

[0352] The analog video signal output from V.DAC 67 and the analog audiosignal output from A.DAC 69 are supplied to an external component (notshown; a multi-channel stereo system having two to six channels+monitorTV or projector) via AV output section 46.

[0353] OSD data output from MPU 30 is input to video processor 66 indecoder unit 60. The OSD data is superimposed on main picture data, andthey are supplied to an external monitor TV connected to AV outputsection 46. Thus, various kinds of text information are displayedtogether with main picture data.

[0354] The data processes in the RTR video recorder are roughlycategorized into two processes, i.e., a recording process and playbackprocess.

[0355]FIG. 30 is a flow chart for explaining an example of the recordingoperation in the RTR video recorder shown in FIG. 29.

[0356] Upon receiving an image recording command input by remotecontroller operation of the user or a timer recording program (notshown), MPU 30 reads management data (file system and the like) fromdisc 10 (FIG. 1) set in disc drive 32 (step ST10), and determines therecording area (write area).

[0357] If disc 10 has no unrecorded area with a minimum required size oran area that can be erased by overwriting data, i.e., if no free spaceexists (NO in step ST12), MPU 30 displays an alert message “no space isavailable for recording” (step ST14), thus stopping recording.

[0358] If a free space exists (YES in step ST12), MPU 30 determines awrite address (step ST16), and writes data required for recording(writing) on the determined area in the management area (RTR_VMG fileand the like) (step ST18).

[0359] MPU 30 then executes an initial setting process for recording(step ST20). More specifically, MPU 30 sets the average transfer rate(e.g., 4 Mbps) in the respective encoders in encoder unit 50 shown inFIG. 29, resets STC 38 to a predetermined value (e.g., zero), sets awrite start address in drive 32, initializes formatter 56 (e.g., forNTSC recording based on MPEG2 /4 Mbps), enters dummy packs (FIGS. 3 and4), sets the segmentation time of cells to be a predetermined value, andsets the number C_EPI_Ns (FIG. 24) of pieces of cell entry pointinformation to zero.

[0360] Upon completion of the aforementioned initial setting process,MPU 30 sets a recording start command in the respective encoders inencoder unit 50 to start recording (step ST22), and starts a recordprocess (step ST23).

[0361] The flow of a video signal in the record process (step ST23) isas follows.

[0362] An AV signal input to external AV input section 42 or a broadcastsignal received by TV tuner 44 are A/D-converted by ADC 52. TheA/D-converted digital video signal is input to V encoder 53, and thedigital audio signal is input to A encoder 54. Also, a closed captionsignal or text signal such as teletext or the like contained in thebroadcast signal is input from TV tuner 44 to SP encoder 55.

[0363] The respective encoders compress the input signals by apredetermined method and packetize them to have 2,048 bytes per pack,and input packets to formatter 56.

[0364] Note that the respective encoders determine PTS (presentationtime stamp or playback time stamp) and DTS (decoding time stamp) of eachpacket in accordance with the count value from STC 38, as needed, uponrecording.

[0365] Formatter 56 temporarily stores packet data in buffer memory 57,then packs the input packet data, mixes them in units of GOPs, andtransfers the packs to data processor 36.

[0366] Data processor 36 forms groups of 16 transferred packs (2kbytes), executes an ECC process of these packs using, e.g., a productcode, and sends them to disc drive 32.

[0367] At this time, when disc drive 32 is not ready to record, dataprocessor 36 transfers the recording signal to the temporary storagebuffer, and waits until disc drive 32 is ready to record data. When discdrive 32 is ready to record data, drive 32 starts recording.

[0368] In this case, a large-size memory is used as temporary storagebuffer 34 so as to store recording data for several minutes or more byhigh-speed access.

[0369] During the record process, a process for automatically enteringentry points at prescribed time intervals (e.g., at 5-sec intervals) isdone (step ST25; see FIG. 33). The user can arbitrarily set this entrypoint entering time interval in units of minutes. If this time intervalis set to be longer than the free space (recordable time) of disc 10, noentry points are automatically entered.

[0370] During recording (NO in step ST27), if the user requires enteringof an entry point (YES in step ST29), a process for entering an entrypoint is done (step ST31; see FIG. 31) independently of the process instep ST25.

[0371] For example, when a remote controller (not shown) has an entrypoint key, and the user has pressed this entry point key during therecord process, entry point information (FIG. 25) is entered at aposition corresponding to the recorded contents at that time.

[0372] At this time, MPU 30 records entry point information inmanagement information (RTR_VMG file in FIG. 5) in response to the entrypoint enter request from the user or set (RTR video recorder).

[0373] Upon completion of recording (YES in step ST27), MPU 30initializes the respective encoders and formatter in encoder unit 50,sends predetermined management information to drive 32, and records itin RTR_VMGI of disc 10 (step ST34).

[0374]FIG. 31 is a flow chart for explaining an example of the playbackoperation in the RTR video recorder shown in FIG. 29.

[0375] Upon receiving a playback command input by remote controlleroperation by the user or a timer playback program (not shown), MPU 30reads the contents of the management area (RTR_VMG) of disc 10 via drive32 and data processor 26 (step ST40), and determines the playbackaddress.

[0376] MPU 30 selects a program chain and programs to be played back onthe basis of the read management data (step ST42), and sets a playbackstart command in the respective decoders in decoder unit 60 (step ST44).

[0377] MPU 30 then sends the determined playback address and readcommand to drive 32 and starts a playback process (step ST46).

[0378] Drive 32 reads out sector data of disc 10 (FIG. 1) in accordancewith the received read command, and data processor 36 corrects errors ofreadout data, and outputs the data to decoder unit 60 in the form ofpack data.

[0379] In decoder unit 60, separator 62 receives the readout pack data.Separator 62 packetizes the received data, and transfers packets inaccordance with the types of data (video data, audio data, sub-picturedata, and the like). That is, separator 62 transfers video packet data(MPEG video data) to V decoder 64, audio packet data to A decoder 68,and sub-picture data to SP decoder 65.

[0380] At the beginning of transfer of packet data to the respectivedecoder, SCR (system clock reference or reference system clock) data isloaded onto STC 38. The respective decoders execute playback processesin synchronism with PTS values (see FIG. 3) in packet data (that is, bycomparing PTS and STC values). In this manner, a moving picture withaudio and superimposed dialog data, which are synchronous with a video,can be played back.

[0381] If playback from an entry point of a specific. cell is requiredduring playback (YES in step ST50), MPU 30 converts EP_PTM (see FIG. 25)of the target entry point into a file pointer with reference to TMAP(see FIG. 14), and accesses a VOBU (see FIG. 28) corresponding to thatentry point (step ST52).

[0382] If playback from an entry point is not required (NO in stepST50), the playback process continues.

[0383] If enter of an entry point is required during the playbackprocess (YES in step ST54), a process for entering an entry point can beexecuted (step ST31). This entry point enter process can have the samecontents as that (ST31 in FIG. 30) upon recording.

[0384] If playback is to end (YES in step ST48), MPU 30 waits forcompletion of playback of the VOBU, playback of which is in progress atthat time, and then sets the respective decoders in decoder unit 60 uponstopping decoding (step ST58), thus ending the playback process.

[0385]FIG. 32 is a flow chart for explaining an example of a processexecuted when recording or playback of the RTR video recorder(recorder/player) is underway, and the user or recorder/player requestsenter of an entry point with respect to specific video or audio data.This entry point enter process corresponds to step. ST31 in FIG. 30 or31.

[0386] Upon receiving the entry point enter request from the user orrecorder/player (step ST310), MPU 30 of the RTR video recorder(recorder/player) shown in FIG. 29 increments C_EPI_Ns (FIG. 24) inmovie cell general information M_C_GI by “1” (step ST312).

[0387] If no entry point enter request is input, C_EPI_Ns is set at “0”.

[0388] Incrementing C_EPI_Ns by “1” means addition of one entry pointinformation in a cell of a program whose recording (or playback) isunderway. Hence, MPU 30 assures an area for movie cell entry pointinformation (M_C_EPI) in movie cell information (M_CI).

[0389] Assume that the user has made a text input or the recorder/playerhas given closed caption data or the like of a broadcast program,air-check of which is underway, as a text input within a predeterminedperiod of time (e.g., within 30 sec) after that (YES in step ST314).

[0390] Note that the text input is not limited to a character input butincludes an operation result input when the user has selected a menuitem or has clicked a mouse button.

[0391] MPU 30 sets “1” in entry point type EP_TY in movie cell entrypoint information M_C_EPI (step S316). EP_TY=“1” indicates that M_C_EPIincludes primary text information PRM_TXTI.

[0392] Subsequently, MPU 30 reads the current count value of STC 38 andwrites the read value in entry point playback time EP_PTM (FIG. 25) inM_C_EPI (step ST320).

[0393] Furthermore, MPU 30 reads the current time (year, month, day,hour, minute, and second) from timepiece unit 40, and writes the readvalue in an information date (FIG. 25) in primary text informationPRM_TXTI in M_C_EPI (step ST322).

[0394] After that, MPU 30 writes the following attribute data (one of 0to 7) in information type [1] in primary text information PRM_TXTI (stepST324):

[0395] information type [1]=0, user mark (the user enters an entrypoint)

[0396] information type [1]=1; set mark (the recorder/player enters anentry point)

[0397] information type [1]=2; defect start mark

[0398] information type [1]=3; defect end mark

[0399] information type [1]=4; presentation start mark

[0400] information type [1]=5; presentation end mark

[0401] information type [1]=6; erasure prohibition mark

[0402] information type [1]=7; another mark (e.g., an instruction fromother than the user or recorder/player).

[0403] Note that [1] in information type [1] means the first data fieldof the information type. If this data field has a 3-bit configuration,information type [1] can express eight different attributes; if it hasan 8-bit configuration, 256 different attributes.

[0404] More specifically, when the user requests enter of an entrypoint, information type [1]=0; when the recorder/player, i.e., the RTRvideo recorder set requests enter of an entry point, information type[1]=1.

[0405] Information type [1]=2 is set for a defect start mark (to bedescribed later), and information type [1]=3 is set for a defect endmark.

[0406] Also, information type [1]=4 is set for a presentation start mark(to be described later), and information type [1]=5 is set for apresentation end mark.

[0407] Information type [1]6 is set for an erasure prohibition mark (tobe described later).

[0408] Furthermore, information type [1]=7 is set when the entry pointenter request is sent from a broadcast station during recording of abroadcast program or is sent from a communication partner duringdownloading of digital video data via a communication line.

[0409] If no text input is made for the entry point in the entry pointenter process (NO in step ST314), “0” is set in EP_TY (step ST318).

[0410] MPU 30 sets “0” in EP TY in movie cell entry point informationM_C_EPI (step ST316). EP_TY=“0” indicates that primary text informationPRM_TXTI in M_C_EPI is empty.

[0411] In this case, MPU 30 sets PTS in EP_PTM (step ST330), and setspredetermined contents in information type [1] in PRM_TXTI (step ST324),thus ending the entry point enter process.

[0412]FIG. 33 is a flow chart for explaining an example of an automaticentry point enter process (for entering entry points at given timeintervals) in the RTR video recorder shown in FIG. 29.

[0413] In this process, entry points are automatically entered atprescribed time intervals (without interrupting recording) irrespectiveof the contents of video picture or audio data to be recorded.

[0414] Before the start of recording, the user executes an initialsetting process. That is, the user sets a numerical value of parameter awhich designates the entry point enter interval in units of minutes, andindex parameter n is preset to “1” (step ST200).

[0415] If the user does nothing, a predetermined default value (forexample, a=5 indicating 5-min intervals, a=0 that prohibits entry pointsfrom being automatically entered, or the like) is selected, and n ispreset to “1”.

[0416] If recording is started after the initial setting process at thestart of recording, the process for entering entry points at prescribedintervals is executed at, e.g., the timing of step ST25 in FIG. 30.

[0417] That is, STC indicating an elapse of recording time is comparedwith a (n(5400000 (corresponding to an minutes when 90-kHz clocks areused) (step ST250).

[0418] If an minutes (initially, an =5 min) have not elapsed yet afterthe start of recording (NO in step ST250), the control returns to therecord process in step ST23 in FIG. 30.

[0419] If an minutes (an=5 min) have elapsed after the start ofrecording (YES in step ST250), the entry point enter process with thecontents that have been explained with reference to, e.g., FIG. 32 isexecuted (step ST31).

[0420] If the entry point at that time (when 5 minutes have elapsedafter the start of recording) has been entered, index parameter n isincremented by “1” (step ST252), and the control returns to the recordprocess in step ST23 in FIG. 30.

[0421] If an minutes (next, an=10 min) have not elapsed yet after thestart of recording (NO in step ST250), the control returns to the recordprocess in step ST23 in FIG. 30.

[0422] If an minutes (an=10 min) have elapsed after the start ofrecording (YES in step ST250), the entry point enter process with thecontents that have been explained with reference to, e.g., FIG. 32 isexecuted (step ST31).

[0423] The aforementioned processes are repeated until recording iscompleted. As a result, when a television broadcast program for 54 minis recorded, 10 entry points are automatically recorded at 5-minintervals.

[0424] Note that the RTR video recorder automatically enters entrypoints at the start of recording, at the end of recording, at the pauseof recording, at the start of playback, at the end of playback, at thepause of playback, upon switching video picture data to be recorded,upon switching video audio data to be recorded, and so forth, inaddition to the aforementioned process for entering entry points atgiven time intervals irrespective of recorded contents.

[0425] For example, whether or not the audio level of the recordingsource has changed (whether or not a predetermined audio level or lowercontinues for a predetermined period of time) is detected, and an entrypoint can be automatically entered at that detection position.

[0426] Alternatively, a scene change is detected from a change in MPEGvideo data in the recording source (when the image contents have changeddrastically due to a scene change, since the moving picture compressionratio lowers, the buffer capacity in an MPEG encoder is consumedabruptly within a short period of time), and an entry point can beautomatically entered at that detection position.

[0427]FIG. 34 is a flow chart for explaining an example of the textinformation input process in the RTR video recorder shown in FIG. 29.

[0428] MPU 30 reads management data (RTR_VMG and the like in FIGS. 5 and6) from disc 10 (step ST100). As a result of reading this data, MPU 30can detect the play list information contents (FIGS. 8 to 11), PGCinformation contents (FIGS. 19 to 21), and contents of movie cellinformation M_CI (FIGS. 23 to 25), as needed.

[0429] MPU 30 reads the contents of movie cell entry point informationM_C_EPI of all the entry points from the read management data (stepST102).

[0430] More specifically, MPU 30 selectively extracts entry points withentry point type EP_TY=“01b” (with primary text information PRM_TXTI)from M_C_EPI (FIG. 25) of the individual entry points. Then, MPU 30reads entry point playback time EP_PTM and primary text informationPRM_TXTI from the entry point information with PRM_TXTI. Furthermore,MPU 30 reads the information type, information date, and textinformation of that entry point from read PRM_TXTI.

[0431] This M_C_EPI read process is repeated if unprocessed entry pointsstill remain (NO in step ST104).

[0432] If all entry points have undergone the M_C_EPI read process (YESin step ST104), MPU 30 outputs input menu information to the monitor onthe basis of the read contents (step ST106).

[0433] In this input menu, for example, as shown in FIG. 35, playbacktimes (hour, minute) based on EP_PTM, titles based on text informationin PRM_TXTI, thumbnail images based on THM_PTRI (FIG. 10), attributesbased on the information types in PRM_TXTI, and mark recording dates(year, month, day, hour, minute, and second) based on the informationdates in PRM_TXTI are displayed while being catogorized in units ofitems and are sorted in the order of playback times (or recordingtimes).

[0434] The user moves the cursor to a predetermined line position of atitle field in the menu using the cursor keys of a remote controller(not shown), an optional keyboard, or the like, and selects an entrypoint or points which is or are to undergo text input (step ST108). Inthis manner, the user can input desired text to a target entry point orpoints by operating the remote controller or keyboard (step ST110).

[0435] The aforementioned text input is done for all the entry pointsthe user wants (YES in step ST112, ST106 to ST110).

[0436] If the text input is complete for all the entry points the userwants (NO in step ST112), text information (FIG. 25) in PRM_TXTI ofM_C_EPI is updated to the contents exemplified in FIG. 35 (step ST114),and the updated data is written in a predetermined area of themanagement data (RTR_VMG) (step ST116).

[0437] In this fashion, the user inputs his or her desired textinformation or the like to an entry point or points he or she wants, andthe input contents are entered in disc 10 (FIG. 1).

[0438]FIG. 36 depicts a state wherein information exemplified in FIG. 35has been entered in disc 10 by the processes shown in FIG. 34.

[0439] Referring to FIG. 36, attribute “10” of an entry point at thestart of recording (recording time 00′00″) and attribute “10” of anentry point at the end of recording (recording time 02′00″) indicatethat the RTR video recorder has automatically entered entry points. Notethat the recording date is written on the basis of time data fromtimepiece unit 40 in FIG. 29, and text “Cinderella” is extracted fromclosed caption data at the beginning of a broadcast program (broadcastwith text) and is automatically written.

[0440] Entry points at three positions of recording times 00′30″,01′00″, and 01′10″ of the disc indicate overwritten recorded portions inthe middle of the recorded program “Cinderella” by user operations. Forthis reason, the attributes of these entry points are “00′” indicatingthe user mark, and their recording dates are largely different from thatof “Cinderella”.

[0441] At each entry point entered by the user, an image (obtained byreducing the I-picture of MPEG) at that position is extracted as athumbnail, which is entered in THM_PTRI of play list search pointerPL_SRP (FIG. 10) as one entry point data.

[0442]FIG. 37 exemplifies a case wherein the user inputs text at eachentry point in place of the thumbnails entered, as shown in FIG. 36, andtext information is entered in PRM_TXTI (FIG. 25) of movie cell entrypoint information M_C_EPI.

[0443]FIG. 38 is a flow chart for explaining an example of the playbackmenu display process in the RTR video recorder shown in FIG. 29.

[0444] MPU 30 reads management data (RTR_VMG and the like) from disc 10(step ST700). As a result of reading this data, MPU 30 can detect theplay list information contents (FIGS. 8 to 11), PGC information contents(FIGS. 19 to 21), and contents of movie cell information M_CI (FIGS. 23to 25), as needed.

[0445] MPU 30 reads the contents of movie cell entry point informationM_C_EPI of all the entry points from the read management data (stepST702).

[0446] More specifically, MPU 30 selectively extracts entry points withentry point type EP_TY=“01b” (with primary text information PRM_TXTI)from M_C_EPI (FIG. 25) of the individual entry points. Then, MPU 30reads primary text information PRM_TXTI, and information [1] of thatentry point.

[0447] The description contents of this information type [1] are:

[0448] information type [1]=0, user mark (the user enters an entrypoint)

[0449] information type [1]=1; set mark (the recorder/player enters anentry point)

[0450] information type [1]=2; defect start mark

[0451] information type [1]=3; defect end mark

[0452] information type [1]=4; presentation start mark

[0453] information type [1]=5; presentation end mark

[0454] information type [1]=6; erasure prohibition mark

[0455] information type [1]=7; another mark (e.g., an instruction fromother than the user or recorder/player).

[0456] If read information type [1] is “0” (user mark) or “1” (set mark)(YES in step ST703), MPU 30 further reads the information date and textinformation from primary text information PRM_TXTI (step ST704).

[0457] If read information type [1] is neither “0” nor “1” (NO in stepST703), the control skips step ST704.

[0458] The M_C_EPI information read process (ST702 to ST704) is repeatedif unprocessed entry points still remain (NO in step ST706).

[0459] By repeating this process, MPU 30 can fetch all pieces of moviecell information at entry points of the user marks or set marks.

[0460] If all entry points have undergone the M_C_EPI read process (YESin step ST706), MPU 30 outputs playback menu information to the monitoron the basis of the read contents (step ST708).

[0461] In this playback menu, for example, as shown in FIG. 39, playbacktimes (hour, minute) based on EP_PTM, titles based on text informationin PRM_TXTI, thumbnail images based on THM_PTRI (FIG. 10), attributesbased on the information types in PRM_TXTI, and mark recording dates(year, month, day, hour, minute, and second) based on the informationdates in PRM_TXTI are displayed while being categorized in units ofitems and are sorted in the order of playback times (or recordingtimes).

[0462] The user moves a title select cursor to a desired line positionin the playback menu by operating the cursor keys of a remote controller(not shown) and selects an entry point to be played back (step ST710).

[0463] MPU 30 converts the entry point playback time value of theselected entry point into a corresponding file pointer on the basis oftime map information (FIGS. 14 to 16) (step ST712). Using this filepointer, the entry point playback time value is converted into aphysical address (VOBU address) by the file system, thus startingplayback.

[0464]FIG. 40 is a flow chart for explaining an example of the textinformation search process in the RTR video recorder shown in FIG. 29.

[0465] MPU 30 executes a process for displaying the playback menu usedto input a search keyword (step ST400).

[0466] This playback menu for search is used when the user inputs akeyword upon searching information recorded in M_C_EPI (FIG. 25) ofrespective entry points.

[0467] For example, assume that the user inputs search keywords tosearch for all entry points which include a character string“Cinderella” in their titles and were marked on January 1999 (stepST402), as shown in FIG. 41.

[0468] MPU 30 reads management data (RTR_VMG) from disc 10, and acquiresthe contents of movie cell information M_CI of all the recorded entrypoints (step ST404).

[0469] MPU 30 then extracts M_C_EPI from the acquired information, andreads the information date and text information from PRM_TXTI (FIG. 25)in that information (step ST406).

[0470] MPU 30 searches based on the keywords (to search for entry pointswhich include a character string “Cinderella” and were marked on January1999) set by the user.

[0471] As a result, if an entry point that is a match to the keywords isfound (YES in step ST408), MPU 30 reads information type [1] of thatentry point from PRM_TXTI of the entry point (step ST410).

[0472] The description contents of this information type [1] are:

[0473] information type [1]=0, user mark (the user enters an entrypoint)

[0474] information type [1]=1; set mark (the recorder/player enters anentry point)

[0475] information type [1]=2; defect start mark

[0476] information type [1]=3; defect end mark

[0477] information type [1]=4; presentation start mark

[0478] information type [1]=5; presentation end mark

[0479] information type [1]=6; erasure prohibition mark

[0480] information type [1]=7; another mark (e.g., an instruction fromother than the user or recorder/player).

[0481] Based on the contents of read information type [1], entry pointswith information type [1] other than “1” can be excluded from the searchresults, and only entry points written by the RTR video recorder uponrecording can be left as search results.

[0482] Alternatively, if read information type [1] is “2” (or 2X; X isan arbitrary integer value) or 3 (or 3X), a defect (e.g., ECC errorcorrection failure upon playback or the like) is present at therecording position of the cell corresponding to that entry point, andsuch entry point can be excluded from search results in some cases.

[0483] If the search is complete and no entry point to be searchedremains (YES in step ST412), MPU 30 displays the search results on themonitor, as shown in, e.g., FIG. 42 (step ST414).

[0484] MPU 30 converts the entry point playback time value of each entrypoint found by search into a corresponding file pointer on the basis oftime map information (in FIGS. 14 to 16) (step ST418). Using this filepointer, the entry point playback time value can be converted into aphysical address (VOBU address) by the file system, and only an entrypoint mark portion found by search can be selectively played back.

[0485]FIG. 43 is a flow chart for explaining an example of the defectenter process in the RTR video recorder shown in FIG. 29.

[0486] This defect enter process is executed, for example, when the userwants to check an old disc.

[0487] MPU 30 reads management data (RTR_VMG) (step ST500), and resets adefect flag to “0” (step ST502).

[0488] This defect flag can be set in a given field of the internal RAMor register of MPU 30.

[0489] Then, MPU 30 plays back disc 10 (step ST504). This playbackprocess is the same as that in step ST46 in FIG. 31.

[0490] Initially, the defect flag is “0” (YES in step ST506). Duringplayback, if no defect (ECC error correction failure) is found (NO instep ST508), and playback is not terminated (NO in step ST516), playbackis normally continued (loop of steps ST504 to ST516).

[0491] If any defect (ECC error correction failure) is found duringplayback (YES in step ST508), MPU 30 increments the number C_EPI_Ns(FIG. 24) of pieces of cell entry point information by “1”, sets “1” inentry point type EP_TY (FIG. 25), sets PTS (FIG. 3) at that time inentry point playback time EP_PTM (FIG. 25), and sets current date (datedata from timepiece unit 40) in the information date (FIG. 25) inprimary text information PRM_TXTI (step ST510).

[0492] Then, MPU 30 sets 2X (X is an arbitrary integer value) in theinformation type in primary text information PRM_TXTI (step S512). Withthis information type set with 2X, the defect start point is entered.

[0493] If a defect is found for the first type, 2X of information typeis set to be “20”. If the second defect is found, 2X=21; if the thirddefect is found, 2X=22.

[0494] Upon completion of entering of the defect start points, MPU 30sets the defect flag at “1” (step ST514).

[0495] If playback is not terminated (NO In step S516), playbackcontinues (step ST504).

[0496] Since the defect flag is set at “1” immediately beforecontinuation of playback (NO in step ST506), the control enters anotherprocessing loop in turn.

[0497] The presence/absence of defects (the presence/absence of ECCerror correction failures) is checked. If a defect still continues to bedetected (YES in step ST518), and playback is not terminated (NO in stepS526), MPU 30 transfers data that informs the user that playback of adefective portion is in progress to video decoder 64. Then, alertcharacters or mark “playback of defective portion now in progress” aredisplayed on the blue back on the monitor screen (not shown) (stepST528). Alternatively, if I-picture data (free from any defect)immediately before the defect flag is set at “1” remains on a videobuffer (not shown) of decoder unit 60, that I-picture data may betransferred to video decoder 64 for the purpose of informing the userthat playback of a defective portion is in progress.

[0498] If the defect disappears after the defect flag is set at “1” (ECCerror correction has succeeded), that position corresponds to the endpoint of the defective portion.

[0499] If playback of the defective portion comes to an end, and ECCerror correction recovers normal function (NO in step ST518), MPU 30increments the number C_EPI_Ns (FIG. 24) of pieces of cell entry pointinformation by “1”, sets “1” in entry point type EP_TY (FIG. 25), setsPTS (FIG. 3) at that time in entry point playback time EP_PTM (FIG. 25),and sets current date (date data from timepiece unit 40) in theinformation date (FIG. 25) in primary text information PRM_TXTI (stepST520).

[0500] MPU 30 then sets 3X (X is an arbitrary integer value) in theinformation type (FIG. 25) in primary text information PRM_TXTI (stepST522). With the information type set with 3X, the defect end point isentered.

[0501] If a defect is found for the first type, 3X of information typeis set to be “30”. If the second defect is found, 3X=31; if the thirddefect is found, 3X=33.

[0502] Note that 2X (20, 21, 22, . . . ) in step S512 is paired with 3X(30, 31, 32, . . . ) in step ST522. More specifically, a pair ofinformation types “20” and “30” are assigned to the first defect asthose of the entry points of the defect start and end points.

[0503] Upon completion of entering of the defect end point, MPU 30resets the defect flag to “0” (step ST524).

[0504] After that, if playback is not terminated (NO in step S526),playback continues (step ST504).

[0505] Since the defect flag is “0” in this case, the loop of stepsST504 to ST516 is executed until a new defective portion begins to beplayed back.

[0506] If playback is terminated without any defects (NO in step ST508,YES in step ST516), no information type=2X is entered, and only aninformation type 3X is entered (step ST522). In this case, entry pointsdo not form any pairs mentioned above. This record shows that no defectis found during playback of the disc.

[0507]FIG. 44 shows an example of entry points when two defects arefound by the process shown in FIG. 43.

[0508] If the defect positions of the disc of interest can be detectedbeforehand based on pairs of information types (contents of PRM_TXTI inFIG. 25) entered in steps ST512 and ST522 in FIG. 43, how to play backsuch defective portions can also be determined. Hence, a menu thatprompts the user to select a defective portion reproduction manner isneeded. FIG. 45 shows an example of such defect management menu.

[0509] More specifically, even when the disc of interest has a defect,and suffers many MPEG block noise components (or digital audio data isdistorted and sometimes discontinued), if the user wants to play back toconfirm the contents of that portion, he or she can select areproduction manner “incomplete video playback”.

[0510] When a defect is disagreeable to see, the user can select areproduction manner “skip that portion, and display alert on blue backon monitor”.

[0511] Alternatively, in place of alert display on the blue back, theuser may select a reproduction manner “display alert while displayingstill image of I-picture immediately before error has occurred asbackground image”.

[0512] The data that pertain to the reproduction manners can be enteredanywhere (e.g., as a kind of information type) in M_C_EPI in FIG. 25.

[0513]FIG. 46 is a flow chart for explaining an example of the processfor entering the priority order of erasure in the RTR video recordershown in FIG. 29.

[0514] MPU 30 reads management data (RTR_VMG and the like) from disc 10(step ST600). As a result of reading this data, MpU 30 can detect theplay list information contents (FIGS. 8 to 11), PGC information contents(FIGS. 19 to 21), and contents of movie cell information M_CI (FIGS. 23to 25), as needed.

[0515] MPU 30 reads the contents of movie cell entry point informationM_C_EPI of all the entry points from the read management data (stepST602).

[0516] More specifically, MPU 30 selectively extracts entry points withentry point type EP_TY=“01b” (with primary text information PRM_TXTI)from M_C_EPI (FIG. 25) of the individual entry points. Then, MPU 30reads primary text information PRM_TXTI, and information [1] of thatentry point.

[0517] The description contents of this information type [1] are:

[0518] information type [1]=0, user mark (the user enters an entrypoint)

[0519] information type [1]=1; set mark (the recorder/player enters anentry point)

[0520] information type [1]=2;defect start mark

[0521] information type [1]=3; defect end mark

[0522] information type [1]=4; presentation start mark

[0523] information type [1]=5; presentation end mark

[0524] information type [1]=6; erasure prohibition mark

[0525] information type [1]=7; another mark (e.g., an instruction fromother than the user or recorder/player).

[0526] If read information type [1] is “4” (presentation start mark) or“6” (erasure prohibition mark) (YES in step ST603), MPU 30 further readsthe information date and text information from primary text informationPRM_TXTI (step ST604).

[0527] If read information type [1] is neither “4” nor “6” (NO in stepST603), the control skips step ST604.

[0528] The M_C_EPI information read process (ST602 to ST604) is repeatedif unprocessed entry points still remain (NO in step ST606).

[0529] By repeating this process, MPU 30 can fetch all pieces of moviecell information at entry points of the presentation start marks orerasure prohibition marks.

[0530] If all entry points have undergone the M_C_EPI read process (YESin step ST606), MPU 30 outputs erasure (or delete) menu information tothe monitor on the basis of the read contents (step ST608).

[0531] In this erasure menu, for example, as shown in FIG. 48, playbacktimes (hour, minute) based on EP_PTM, titles based on text informationin PRM_TXTI, thumbnail images based on THM_PTRI (FIG. 10), attributesbased on the information types in PRM_TXTI, playback dates (year, month,day, hour, minute, and second) based on the information dates inPRM_TXTI, and the erasure order (or erasure prohibition marks) based oninformation type [0] of PRM_TXTI are displayed while being categorizedin units of items and are sorted in the order of playback times (orrecording times).

[0532] Note that a pair of information type [0]=4X (erasure start point)and information type [0]=5X (erasure end point) are set as informationtype [0], as exemplified in the attribute fields of entry points in FIG.47.

[0533] In information type [0], identical values are written in turnfrom “0” in pairs of movie cell information, but the same value as thatof another pair of movie cell information must not be written.

[0534] For example, in FIG. 47, a recorded video (recording time=15 minfrom 00′30″ to 00′45″) with a title “peace”, which has a pair of entrypoint attributes (information type [0]) “40” and “50” has the firsterasure order on the erasure menu in FIG. 48, if the remaining size ofthe disc becomes short during recording, this recorded video with thetitle “peace” is erased at the very beginning by overwriting anotherdata.

[0535] The user moves the cursor to a predetermined position of anerasure order field in the menu in FIG. 48 using the cursor keys of aremote controller (not shown), an optional keyboard, or the like, andselects entry points, the erasure order of which is to be changed.

[0536] If the user wants to set a lower erasure order of a cellcorresponding to the selected entry points (YES in step ST610), he orshe decreases the order of information type [0] of each entry point tobe changed by “1” (for both entry points with information type [1]=4 andinformation type [1]=5) (for example, to change the erasure order fromthe second to the third) (step ST612).

[0537] Conversely, if the user wants to set a higher erasure order, heor she increases the order of information type [0] of each entry pointto be changed by “1” (for both entry points with information type [1]=4and information type [1]=5) (for example, to change the erasure orderfrom the second to the first) (step ST612).

[0538] If the erasure order is not to be changed (NO in step ST610), anderasure is to be prohibited (YES in step ST614), information type [1] ofthat entry point is set at “6” (erasure prohibition mark) (step ST616).

[0539] Upon completion of the erasure order change or erasureprohibition mark set process (YES in step ST618), management data(RTR_VMG) written with information corresponding to PRM_TXTI shown inFIG. 25 is written in disc 10 (step ST620).

[0540] If the remaining size of disc 10 becomes short during recording,MPU 30 can proceed with recording while erasing some data on disc 10 byoverwriting in units of entry points in the erasure order (or inascending order of recording dates or playback dates if no erasure orderis set).

[0541]FIG. 49 shows a stream pack structure used when a streamer is usedfor the DVD-RTR recorder. As shown in the figure, one stream pack (2048bytes) is formed of a pack header (14 bytes) and a stream PES packet(2034 bytes).

[0542] The pack header of the stream pack has 14 bytes in size. In thispack header, a pack start code is described in the first 4 bytes(000001Bah). In the next 6 bytes, reference information of system clockreference SCR (SCR_base with 32 bits total) defined by a provider,marker bits, and extension of system clock reference (SCR extension with9 bits) are described. In the subsequent 3 bytes (0189C3h), a programmultiplexed rate (program_mux_rate with 22 bits) and marker bits aredescribed. In the last 1 byte (F8h), a pack stuffing length(pack_stuffing_length with 3 bits) is described, and a reserved area of5 bits is further provided.

[0543] The 32nd bit of SCR_base is set to zero. The program_mux_rate isset to 10.08 Mbps.

[0544] In stream recording, an application performs its own stuffing, sothat the pack length adjustment methods of DVD-VIDEO or DVD-VR (DVDvidec recording) need not be used. In stream recording, it is safe toassume that the stream packs will always have the necessary length.

[0545] A stream PES packet of the stream pack has the following datastructure.

[0546]FIG. 50 illustrates a structure of the stream data area containedin the stream PES packet shown in FIG. 49.

[0547] As shown, one stream PES packet (2034 bytes) includes a PESheader (6 bytes), a substream ID (1 byte), and a stream data area (2027bytes).

[0548] In the PES packet header of the stream PES packet, a packet startcode prefix (packet start code prefix with 24 bits) is recorded at thefirst 3 bytes (000001h). In the next 1 byte, a stream ID(stream_id=10111111b; indicating private stream 2) is recorded. In thesubsequent 2 bytes (07Ech), a PES packet length (PES_packet_length with16 bits) is recorded. In the last 1 byte, a substream ID(sub_stream_id=00000010b; indicating stream recording data) is recorded.

[0549] The stream data area (2027 bytes) within the stream packet ofFIG. 50 includes an application header (9 bytes), an application headerextension (optional), a stuffing byte (optional), and an applicationpacket area.

[0550] The application packet area of FIG. 50 contains one or moreapplication packets each of which is associated with an application timestamp.

[0551] At the leading portion of the application packet area, a partialapplication packet can be recorded. Thereafter, a plurality of pairs ofapplication time stamp ATS and application packet are sequentiallyrecorded. At the trailing portion of the application packet area,another partial application packet can be recorded.

[0552] In other words, at the start of the application packet area, apartial application packet may exist, and at the end of the applicationpacket area, another partial application packet or a stuffing area ofreserved bytes may exist.

[0553] The application time stamp (ATS) arranged in front of eachapplication packet has 32 bits in size. An ATS can be divided into twoparts, namely a base part and an extension part. The base part holds a90 kHz unit value, and the extension part holds the less significantvalue measured in 27 MHz.

[0554] In the structure of FIG. 50, the application header extension maybe used to store information that can differ from application packet toapplication packet. Such information may not be required for all kindsof applications.

[0555] Therefore, a data field of the application header is defined todescribe the presence of the optional application header extension inthe stream data area.

[0556] At stream recording, the first byte of application time stamp ATSof the first application packet should be aligned to the start of theapplication packet area in the first stream packet at the beginning of astream object (SOB).

[0557] Any following stream packets in an SOB may split applicationpackets across stream packet boundaries. The partial application packetsin FIG. 50 show examples obtained by the above splitting.

[0558] The byte offset to the first application time stamp that startsin a stream packet, as well as the number of application packetsstarting in the stream packet, should be described in its applicationheader.

[0559] This mechanism automatically allows for stuffing in front of thefirst application time stamp and after the last application packet in astream packet.

[0560] The above automatic mechanism corresponds to said “an applicationperforms its own stuffing” mentioned in the description for FIG. 49.

[0561] The application header extension (optional) is formed of a listof entries, where there is exactly one entry of 1 byte length for eachapplication packet, which starts in this stream packet. These bytes canbe used to store information that may differ from application packet toapplication packet.

[0562] In the 1 byte application header extension (optional), 1 bitAU_START, 1 bit AU_AND, and 2 bits COPYRIGHT are described.

[0563] When AU_START is set to “1”, this indicates that the associatedapplication packet contains a random access entry point (start of arandom access unit) in the stream.

[0564] When AU_END is set to “1”, this indicates that the associatedapplication packet is the last packet of a random access unit.

[0565] The COPYRIGHT describes the copyright status of the associatedapplication packet.

[0566]FIG. 51 shows entry point relating information with respect tomovie cell information M_CI contained in PGCI of the RTR video manager.

[0567] More specifically, movie cell general information M_C_GIcontained in M_CI includes the number of cell entry point informationC_EPI_Ns (cf. FIG. 24), and movie cell entry point information M_C_EPIcontained in M_CI includes entry point type EP_TY, entry pointpresentation time EP_PTM and primary text information PRM_TXTI (cf. FIG.25). In this PRM_TXTI, the information type, information date and textinformation can be described.

[0568]FIG. 52 shows entry point relating information with respect tostill picture cell information S_CI contained in PGCI of the RTR videomanager.

[0569] More specifically, still picture cell general information S_C_GIcontained in S_CI includes the number of cell entry point informationC_EPI_Ns, and still picture cell entry point information S_C_EPIcontained in S_CI includes entry point type EP_TY, still picture VOBentry number S_VOB_ENTN and primary text information PRM_TXTI. In thisPRM_TXTI, the information type, information date and text informationcan be described.

[0570]FIG. 53 shows entry point relating information with respect tostream cell information SCI contained in PGCI of the RTR stream manager.

[0571] More specifically, stream cell information general informationSCI_GI contained in SCI includes the number of stream cell entry pointinformation SC_EPI_Ns, and stream cell entry point information SC_EPIcontained in SCI includes entry point type EP_TY, application packetarrival time of entry point EP_APAT and primary text informationPRM_TXTI. In this PRM_TXTI, the information type, information date andtext information can be described.

[0572] According to the embodiment (real-time digital videorecording/playback system) of the present invention, the user can writeor erase a mark (entry point) at an arbitrary recording position ofvideo data, audio data, and the like as if he or she placed a bookmarkbetween pages or at an important position while reading a book.

[0573] When information that pertains to the mark (entry point) isrecorded at a predetermined position (movie cell entry point informationor the like) on a medium (disc), the user can enjoy the following meritsusing this information upon playing back or recording (includingoverwrite and erasure).

[0574] 1) An index that indicates programs and their recording positionson a disc can be freely generated.

[0575] That is, when that disc is set in the apparatus, the user caneasily know the recorded contents of marked portions (entry points), andcan start to play back such portions by simple operation.

[0576] 2) A desired program can be easily found by searching variousprogram recorded on a disc.

[0577] That is, when that disc is set in the apparatus (RTR videorecorder), the user can search for titles of the marked portions (entrypoints) using a keyword. As a result of search, the user can easily knowonly a desired program of various ones recorded on the disc, and canstart to play back that portion by simple operation.

[0578] 3) A portion that can be erased (by overwrite recording) (or aportion that is not to be erased) of various programs recorded on a disccan be easily specified.

[0579] That is, when that disc is set in the apparatus, the user caneasily know the priority order of erasure or erasurepermission/prohibition of the marked portions (entry points), and canchange the priority order of erasure or erasure permission/prohibitionof a desired portion by simple operation. A program corresponding to amarked portion which is not prohibited from being erased isautomatically erased by overwriting in accordance with the priorityorder of erasure upon recording new data on that disc.

[0580] 4) When a portion of the recorded disc becomes defective, andcannot be normally played back, the defective portion that cannot benormally played back can be easily specified.

[0581] More specifically, when that disc is set in the apparatus, theuser can easily know if the respective marked positions (entry points)suffer defects. If any defect is found, the reproduction manner of thatportion (skip a defective portion, display the blue back during playbackof a defective portion, play back a still image immediately before adefect until a normal portion is played back, and so forth) can bearbitrarily designated.

[0582] As described above, according to the real-time digital videorecording/playback system of the present invention, even when the sizeof the disc to be recorded increases, the user can easily manage itscontents, and can start recording/playback from a position of his or herchoice.

[0583] Additional advantages and modifications will readily occur tothose skilled in the art. Therefore, the invention in its broaderaspects is not limited to the specific details and representativeembodiments shown and described herein. Accordingly, variousmodifications may be made without departing from the spirit or scope ofthe general inventive concept as defined by the appended claims andtheir equivalents.

What is claimed is:
 1. A data structure having a data area and itsmanagement area, wherein data is stored in said data area in a form ofone or more objects, each said object includes one or more data units,said data unit includes record information in a form of one or morepacks, said record information being presented within a prescribedperiod of time, said management area includes management information formanaging said objects, said management information includes programchain information for specifying an order of presentation of saidobjects, and said program chain information includes one or more piecesof cell information, and wherein said cell information has an area fordescribing information of one or more entry points, each said entrypoint indicating a position to enter said record information.
 2. Thedata structure of claim 1, wherein the information of said entry pointincludes primary text information.
 3. The data structure of claim 1,wherein said primary text information includes at least one of aninformation type, information date and text information.
 4. The datastructure of claim 1, wherein the information of said entry pointincludes entry point type information.
 5. The data structure of claim 1,wherein said cell information includes cell general information, andsaid cell general information includes information indicating a numberof pieces of the entry point information.
 6. The data structure of claim1, wherein said program chain information includes one or more pieces ofprogram information, and said program information includes primary textinformation.
 7. The data structure of claim 6, wherein said primary textinformation includes at least one of an information type, informationdate and text information.
 8. The data structure of claim 1, whereinsaid record information includes video information, and the informationof said entry point includes presentation time information of the entrypoint of said video information.
 9. The data structure of claim 1, wherein said record information includes still picture information, and theinformation of said entry point includes number information of the entrypoint of said still picture information.
 10. The data structure of claim1, wherein said record information includes audio information, and theinformation of said entry point includes information of the entry pointof said audio information.
 11. The data structure of claim 1, whereinsaid management information includes a play list search pointer table,and said a play list search pointer table includes primary textinformation.
 12. The data structure of claim 11, wherein said primarytext information includes at least one of an information type,information date and text information.
 13. The data structure of claim1, wherein said data area stores bitstream data, said pack includes astream packet containing said bitstream data, and said stream packetincludes one or more application packet, each said application packetbeing associated with a predetermined time stamp, and wherein when saidentry point is assigned to any of said application packet, theinformation of said entry point includes information of arrival time ofthe application packet with said entry point.
 14. The data structure ofclaim 13, wherein the information of said entry point includes primarytext information for describing information relating to selected one ormore of the entry points.
 15. The data structure of claim 14, whereinsaid primary text information includes at least one of an informationtype, information date and text information.
 16. The data structure ofclaim 13, wherein the information of said entry point includes entrypoint type information.
 17. An information medium being able to storesaid record information according to the data structure of claim
 1. 18.The information medium of claim 17, wherein said medium is formed of anoptical disc or a semiconductor memory device.
 19. A method for enteringone or more entry points using an information medium, wherein saidinformation medium has a data area and its management area, said dataarea is used for storing data in a form of one or more objects, eachsaid object includes one or more data units, said data unit includesrecord information in a form of one or more packs, said recordinformation being presented within a prescribed period of time, saidmanagement area includes management information for managing saidobjects, said management information includes program chain informationfor specifying an order of presentation of said objects, said programchain information includes one or more pieces of cell information, andsaid cell information has an area for describing information of one ormore entry points, each said entry point indicating a position to entersaid record information. said method comprising a process for enteringsaid entry points with a predetermined time interval when said recordinformation is recorded in the data area of said information medium. 20.A method for entering one or more entry points using an informationmedium, wherein said information medium has a data area and itsmanagement area, said data area is used for storing data in a form ofone or more objects, each said object includes one or more data units,said data unit includes record information in a form of one or morepacks, said record information being presented within a prescribedperiod of time, said management area includes management information formanaging said objects, said management information includes programchain information for specifying an order of presentation of saidobjects, said program chain information includes one or more pieces ofcell information, and said cell information has an area for describinginformation of one or more entry points, each said entry pointindicating a position to enter said record information. said methodcomprising a process for entering said entry points in response to aninstruction from a recorder for recording information on saidinformation medium or from a user of this recorder.
 21. A method forreproducing information from an information medium, wherein saidinformation medium has a data area and its management area, said dataarea is used for storing data in a form of one or more objects, eachsaid object includes one or more data units, said data unit includesrecord information in a form of one or more packs, said recordinformation being presented within a prescribed period of time, saidmanagement area includes management information for managing saidobjects, said management information includes program chain informationfor specifying an order of presentation of said objects, said programchain information includes one or more pieces of cell information, saidcell information has an area for describing information of one or moreentry points, each said entry point indicating a position to enter saidrecord information, said management information further includes a movieAV file information table, said a movie AV file information tableincludes one or more pieces of movie VOB information, said movie VOBinformation includes time map information, said method comprising:reading information of said entry point from said managementinformation; and when a presentation or playback of specific one or onesof said entry points is required, converting a presentation time of thespecific entry point to a corresponding file access pointer using saidtime map information in order to access said specific entry point.
 22. Amethod for inputting text information using an information medium,wherein said information medium has a data area and its management area,said data area is used for storing data in a form of one or moreobjects, each said object includes one or more data units, said dataunit includes record information in a form of one or more packs, saidrecord information being presented within a prescribed period of time,said management area includes management information for managing saidobjects, said management information includes program chain informationfor specifying an order of presentation of said objects, said programchain information includes one or more pieces of cell information, andsaid cell information has an area for describing information of one ormore entry points, each said entry point indicating a position to entersaid record information, the information of one or more said entrypoints being associated with primary text information, said methodcomprising: reading the information of one or more said entry pointsfrom said management information; inputting text information withrespect to a selected one of said entry points; and changing contents ofsaid primary text information according to the input text information.23. A method for displaying a menu using an information medium, whereinsaid information medium has a data area and its management area, saiddata area is used for storing data in a form of one or more objects,each said object includes one or more data units, said data unitincludes record information in a form of one or more packs, said recordinformation being presented within a prescribed period of time, saidmanagement area includes management information for managing saidobjects, said management information includes program chain informationfor specifying an order of presentation of said objects, said programchain information includes one or more pieces of cell information, andsaid cell information has an area for describing information of one ormore entry points, each said entry point indicating a position to entersaid record information, the information of one or more said entrypoints being associated with primary text information, said methodcomprising: reading the information of one or more said entry pointsfrom said management information; reading the primary text informationfrom the read entry point information; and displaying a menu beingassociated with a text or texts with respect to the information of oneor more said entry points.
 24. A method for displaying an erasure ordelete menu using an information medium, wherein said information mediumhas a data area and its management area, said data area is used forstoring data in a form of one or more objects, each said object includesone or more data units, said data unit includes record information in aform of one or more packs, said record information being presentedwithin a prescribed period of time, said management area includesmanagement information for managing said objects, said managementinformation includes program chain information for specifying an orderof presentation of said objects, said program chain information includesone or more pieces of cell information, and said cell information has anarea for describing information of one or more entry points, each saidentry point indicating a position to enter said record information, theinformation of one or more said entry points being associated withprimary text information, said method comprising: reading theinformation of one or more said entry points from said managementinformation; reading the primary text information from the read entrypoint information; and displaying a menu having information with respectto an order of erasure of the record information according to the readentry point information and the read primary text information.
 25. Themethod of claim 24, further comprising: changing said order of erasureof the record information via the displayed menu.
 26. The method ofclaim 24, further comprising: setting said order of erasure of therecord information to an erasure prohibited state, via the displayedmenu.
 27. A method for searching information of an information medium,wherein said information medium has a data area and its management area,said data area is used for storing data in a form of one or moreobjects, each said object includes one or more data units, said dataunit includes record information in a form of one or more packs, saidrecord information being presented within a prescribed period of time,said management area includes management information for managing saidobjects, said management information includes program chain informationfor specifying an order of presentation of said objects, said programchain information includes one or more pieces of cell information, andsaid cell information has an area for describing information of one ormore entry points, each said entry point indicating a position to entersaid record information, the information of one or more said entrypoints being associated with primary text information, said methodcomprising: inputting a key word or key words for searching; searchingthe primary text information containing said key word or key words fromsaid management information; and displaying a result of the searching.28. A method for entering defect of an information medium, wherein saidinformation medium has a data area and its management area, said dataarea is used for storing data in a form of one or more objects, eachsaid object includes one or more data units, said data unit includesrecord information in a form of one or more packs, said recordinformation being presented within a prescribed period of time, saidmanagement area includes management information for managing saidobjects, said management information includes program chain informationfor specifying an order of presentation of said objects, said programchain information includes one or more pieces of cell information, andsaid cell information has an area for describing information of one ormore entry points, each said entry point indicating a position to entersaid record information. said method comprising: reproducing the recordinformation from said data area; when the reproduced informationcontains a defective portion, entering entry point information of astart point of the defective portion as well as entry point informationof an end point of that defective portion.
 29. A recordable/reproducibledigital information medium having a volume space including a data areaand its management area, wherein data is stored in said data area in aform of one or more objects, each said object includes one or more dataunits, said data unit includes record information of video or audio in aform of one or more packs, said record information being presentedwithin a prescribed period of time, said management area includesmanagement information for managing said objects, said managementinformation includes program chain information for specifying an orderof presentation of said objects, said program chain information includesone or more pieces of program information and one or more pieces of cellinformation, said cell information includes specific information forspecifying the object to be presented, said specific information recordsentry point information for describing an entry point of the object tobe reproduced, and said entry point information further includesinformation relating to the entry point.
 30. A digital video informationrecording/reproducing apparatus using a recordable/reproducibleinformation medium having management information for managing objects asrecord information, wherein said management information includes moviecell information, said apparatus comprising: an entry point settingportion for setting a prescribed entry point at said movie cellinformation; an additional information input portion for inputtingadditional information with respect to said entry point; and anadditional information setting portion for setting the input additionalinformation at said entry point.
 31. A method for entering an entrypoint using a recordable/reproducible information medium havingmanagement information for managing objects as record information,wherein said management information includes movie cell information,said method comprising: setting a prescribed entry point at said moviecell information; inputting additional information with respect to saidentry point; and setting the input additional information at said entrypoint.